Resuming a connection in a wireless communication system

ABSTRACT

A user equipment is configured to receive, from a source radio access network, RAN, node with which the user equipment has a connection, a message indicating that the connection is to be suspended and indicating a resume identifier usable by the user equipment to resume the connection after the connection is suspended. While the connection is suspended, the user equipment is configured to transmit to a target RAN node a request to resume the connection. The request includes the resume identifier. The user equipment is also configured to transmit to the target RAN an indication of a public land mobile network, PLMN, with which the resume identifier is associated. Alternatively or additionally, the user equipment is configured to receive a paging message that includes the resume identifier and that indicates the PLMN associated with the resume identifier.

TECHNICAL FIELD

The present application relates generally to a wireless communicationsystem and relates more specifically to resuming a connection in such awireless communication system.

BACKGROUND

In order for a radio access network (RAN) to allocate radio resources toa user equipment (UE), a radio resource control (RRC) connection isestablished between a RAN node and the UE. Establishment of the RRCconnection may involve configuring radio bearers between the RAN nodeand the UE, configuring a security context for the UE, etc. The RAN nodestores this and other information associated with the UE's RRCconnection as a so-called context for the UE (also referred to as UEcontext). The context may therefore contain information needed toestablish and/or maintain the RRC connection, including for instanceinformation about the UE's security context, data radio bearers,connected slices, UE capabilities, etc.

Release of the RRC connection (e.g., after completion of data transfer)correspondingly releases the UE's context at the RAN node, e.g., suchthat the RAN node no longer stores that context. Then, if and when theUE needs another RRC connection (e.g., for transfer of newly arriveddata), the UE must request establishment of a new RRC connection.

Some systems however support suspension of the RRC connection as analternative to complete release of the RRC connection. When the RRCconnection is suspended, the RAN node preserves the context for the UErather than releasing it. This way, the UE can request resumption of theRRC connection by providing the RAN node with a so-called resumeidentifier that the RAN node can use to locate and access the storedcontext for the UE. With access to the stored UE context, the RAN nodeneed not establish an RRC connection from scratch. This in turn reducesUE latency and UE signalling, which further leads to reduced UE energyconsumption.

Some scenarios complicate UE context retrieval. If the UE requestsresumption of its RRC connection at a target RAN node that is differentthan the source RAN node at which the RRC connection was suspended, thetarget RAN node must be able to locate the source RAN node in order toretrieve the UE's context. In a RAN sharing scenario where RAN nodes areshared among different network operators, though, determining which RANnode stores the UE's context proves particularly challenging, especiallyin a way that avoids inefficient coordination between the networkoperators.

SUMMARY

According to some embodiments herein, a resume identifier usable by auser equipment to resume a suspended connection is associated with apublic land mobile network (PLMN). The user equipment thereby indicatesnot only the resume identifier to a target RAN node at which the userequipment requests resumption of the connection, but also indicates thePLMN with which the resume identifier is associated. The target RAN nodecorrespondingly retrieves a context for the connection based on theresume identifier and the indication of the associated PLMN. In someembodiments, associating a PLMN with the resume identifier in this wayresolves any ambiguity that might exist regarding which RAN node storesthe context for the connection, without coordination between RAN sharingoperators and/or without negative impact on user equipment performance(e.g., in terms of battery consumption, delays due to unnecessarysignaling, etc.).

More particularly, embodiments herein include a method performed by auser equipment. The method comprises receiving at the user equipment,from a source radio access network, RAN, node with which the userequipment has a connection, a message indicating that the connection isto be suspended and indicating a resume identifier usable by the userequipment to resume the connection after the connection is suspended.The method also comprises, while the connection is suspended,transmitting from the user equipment to a target RAN node a request toresume the connection, wherein the request includes the resumeidentifier. The method further comprises transmitting from the userequipment to the target RAN node an indication of a public land mobilenetwork, PLMN, with which the resume identifier is associated.

In some embodiments, the method further comprises receiving a pagingmessage that includes the resume identifier and the indication of thePLMN associated with the resume identifier. In this case, transmittingthe request to resume the connection is performed responsive toreceiving the paging message.

Embodiments herein also include a method performed by a target radioaccess network, RAN, node. The method comprises receiving at the targetRAN node a request from a user equipment to resume a connection that wassuspended between the user equipment and a source RAN node. The requestincludes a resume identifier. The method further comprises receiving atthe target RAN node, from the user equipment, an indication of a publicland mobile network, PLMN, with which the resume identifier isassociated. The method also comprises retrieving by the target RAN nodea context for the connection, based on the resume identifier and theindication of the PLMN with which the resume identifier is associated.

In some embodiments, retrieving the context based on the resumeidentifier and the indication comprises identifying, based on the resumeidentifier and the indication of the PLMN with which the resumeidentifier is associated, an interface to a RAN node which maintains thecontext for the connection. In this case, the method further comprisesretrieving, over the identified interface, the context for theconnection.

In other embodiments, retrieving the context based on the resumeidentifier and the indication comprises determining, based on the resumeidentifier and the indication of the PLMN with which the resumeidentifier is associated, that an interface to a RAN node whichmaintains the context for the connection is not available at the targetRAN node. In this case, the method may further comprise selecting, basedon the indication of the PLMN with which the resume identifier isassociated, a core network node that supports the PLMN with which theresume identifier is associated; and transmitting a request for thecontext to the selected core network node, wherein the request includesthe resume identifier.

Embodiments further include a method performed by a source radio accessnetwork, RAN, node. The method comprises establishing a connectionbetween the source RAN node and a user equipment. The method alsocomprises transmitting from the source RAN node a message to the userequipment indicating that the connection is to be suspended andindicating a resume identifier usable by the user equipment to resumethe connection after the connection is suspended. The method furthercomprises transmitting from the source RAN node to the user equipment anindication of a public land mobile network, PLMN, with which the resumeidentifier is associated.

In some embodiments, the method further comprises storing a context forthe connection and storing in the context, or in association with thecontext, the indication of the PLMN with which the resume identifier isassociated.

In the method performed by the target RAN node or the source RAN node,the method may further comprises transmitting a paging message thatincludes the resume identifier and the indication of the PLMN with whichthe resume identifier is associated.

In any of the above methods, the resume identifier in some embodimentsis associated with a RAN node identity that identifies, using a RAN nodeaddressing space shared by different PLMNs, a RAN node which maintains acontext for the connection while the connection is suspended.

In any of the above methods, different PLMNs in some embodiments havethe same set of resume identifiers usable by user equipments to resumesuspended connections.

In any of the above methods, the indication of a PLMN with which theresume identifier is associated in some embodiments is an indication ofa PLMN with which the user equipment is registered or an indication of aPLMN selected by the user equipment.

In any of the above methods, the indication of the PLMN with which theresume identifier is associated in some embodiments comprises an indexof a specific PLMN identity in a list of PLMN identities, wherein eachPLMN identity in the list has an associated index.

Embodiments herein also include corresponding apparatus, computerprograms, and carriers of such computer programs. For example,embodiments herein include a user equipment configured to receive, froma source radio access network, RAN, node with which the user equipmenthas a connection, a message indicating that the connection is to besuspended and indicating a resume identifier usable by the userequipment to resume the connection after the connection is suspended.The user equipment may also be configured to, while the connection issuspended, transmit to a target RAN node a request to resume theconnection, wherein the request includes the resume identifier. The userequipment may be further configured to transmit to the target RAN nodean indication of a public land mobile network, PLMN, with which theresume identifier is associated.

Embodiments also include a radio access network, RAN, node configured tooperate as a target RAN node. The RAN node is configured to receive arequest from a user equipment to resume a connection that was suspendedbetween the user equipment and a source RAN node. The request includes aresume identifier. The RAN node is also configured to receive, from theuser equipment, an indication of a public land mobile network, PLMN,with which the resume identifier is associated. The RAN node is furtherconfigured to retrieve a context for the connection, based on the resumeidentifier and the indication of the PLMN with which the resumeidentifier is associated.

Embodiments further include a radio access network, RAN, node configuredto operate as a source RAN node. The RAN node is configured to establisha connection with a user equipment. The RAN node is also configured totransmit a message to the user equipment indicating that the connectionis to be suspended and indicating a resume identifier usable by the userequipment to resume the connection after the connection is suspended.The RAN node is further configured to transmit to the user equipment anindication of a public land mobile network, PLMN, with which the resumeidentifier is associated.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of a wireless communication system thatincludes a user equipment and RAN nodes according to some embodiments.

FIG. 2 is a block diagram of a wireless communication system thatincludes a user equipment and RAN nodes according to other embodiments.

FIG. 3 is a logic flow diagram of a method performed by a user equipmentaccording to some embodiments.

FIG. 4 is a logic flow diagram of a method performed by a target RANnode according to some embodiments.

FIG. 5 is a logic flow diagram of a method performed by a source RANnode according to some embodiments.

FIG. 6 is a logic flow diagram of a method performed by a RAN nodeaccording to other embodiments.

FIG. 7 is a logic flow diagram of a method performed by a user equipmentaccording to other embodiments.

FIG. 8A is a block diagram of a user equipment according to someembodiments.

FIG. 8B is a block diagram of a user equipment according to otherembodiments.

FIG. 8C is a block diagram of a user equipment according to still otherembodiments.

FIG. 9A is a block diagram of a RAN node according to some embodiments.

FIG. 9B is a block diagram of a RAN node according to other embodiments.

FIG. 9C is a block diagram of a RAN node according to still otherembodiments.

FIG. 9D is a block diagram of a RAN node according to yet otherembodiments.

FIG. 10 is a call flow diagram of a an RRC Connected to RRC Inactivestate transition procedure according to some embodiments.

FIG. 11 is a call flow diagram of an RRC Inactive to RRC Connected statetransition procedure according to some embodiments.

FIG. 12 is a call flow diagram of a procedure to retrieve a UE Contextvia a RAN according to some embodiments.

FIG. 13 is a call flow diagram of a procedure to retrieve a UE Contextvia a 5G CN according to some embodiments.

FIG. 14 is a call flow diagram of a procedure used by a RAN to page a UEvia the 5GC according to some embodiments.

FIG. 15 is a block diagram of a wireless communication network accordingto some embodiments.

FIG. 16 is a block diagram of a user equipment according to someembodiments.

FIG. 17 is a block diagram of a virtualization environment according tosome embodiments.

FIG. 18 is a block diagram of a communication network with a hostcomputer according to some embodiments.

FIG. 19 is a block diagram of a host computer according to someembodiments.

FIG. 20 is a flowchart illustrating a method implemented in acommunication system, in accordance with one embodiment.

FIG. 21 is a flowchart illustrating a method implemented in acommunication system, in accordance with one embodiment.

FIG. 22 is a flowchart illustrating a method implemented in acommunication system, in accordance with one embodiment.

FIG. 23 is a flowchart illustrating a method implemented in acommunication system, in accordance with one embodiment.

DETAILED DESCRIPTION

FIG. 1 shows a wireless communication system 10 according to someembodiments. The system 10 includes a radio access network (RAN) node12-1 (e.g., a base station) and a user equipment (UE) 14. The RAN node12-1 establishes a connection 16 with the UE 14 over a radio interfacein order to connect the UE 14 with a core network (CN) 16A of publicland mobile network (PLMN) A. The CN 16A may in turn connect the UE 14to one or more data networks such as the Internet.

The connection 16 may be a control plane connection such as a radioresource control (RRC) connection. In some embodiments, for instance,the connection 16 is the highest layer in the control plane of an accessstratum (AS) and transfers messages of a non-access stratum (NAS). Inthese and other embodiments, then, the connection 16 may be used forbroadcast of system information, paging, transfer of non-access stratum(NAS) information, access stratum (AS) security configuration, transferof UE radio access capability, measurement configuration and reporting,and/or mobility control. Regardless, with the connection 16 established,the RAN node 12-1 is able to allocate radio resources to the UE 14 andthe UE 14 can correspondingly send or receive user data.

Establishment of the connection 16 may involve configuring radio bearersbetween the RAN node 12-1 and the UE 14, configuring a security contextfor the UE 14, etc. The RAN node 12-1 stores this and other informationassociated with the UE's connection 16 as a so-called context 18A (alsoreferred to as UE context). The context 18A for the connection 16 maytherefore contain information needed to establish and/or maintain theconnection 16, including for instance information about the UE'ssecurity context, data radio bearers, connected slices, UE capabilities,etc.

Release of the connection 16 (e.g., after completion of user datatransfer) releases the context 18A for the connection 16 at the RAN node12-1, e.g., such that the RAN node 12-1 no longer stores that context18A. Where the connection 16 is an RRC connection, for instance, theconnection 16 may be released as part of transitioning the UE 14 fromRRC_CONNECTED state to RRC_IDLE state. Regardless, if and when the UE 14needs another connection (e.g., for transfer of newly arrived userdata), the UE 14 must request establishment of a new connection fromscratch.

In some embodiments, though, the RAN node 12-1 and UE 14 supportsuspension of the connection 16 as an alternative to complete release ofthe connection 16. As shown in this regard, the RAN node 12-1 transmitsto the UE 14 (e.g., after a certain period of UE inactivity) a message20 indicating (e.g., commanding) that the connection 16 is to besuspended. Where the connection 16 is an RRC connection, the UE 14 mayenter an RRC-INACTIVE state after suspending the connection 16.Regardless, the suspend message 20 also includes a resume identifier(ID) 22 that is usable by the UE 14 to resume the connection 16 afterthe connection 16 is suspended. Indeed, rather than releasing thecontext 18A for the connection 16 as done when releasing the connection16, the RAN 12-1 preserves the context 18A for the UE's connection 16;that is, the RAN 12-1 continues to store the context 18A even while theconnection 16 is suspended. Moreover, the RAN node 12-1 maps orotherwise associates the stored context 18A for the connection 16 withthe resume identifier 22. This way, the UE 14 can provide the RAN node12-1 with the resume identifier 22 and the RAN node 12-1 can resume theconnection 16 using the associated context 18A, rather than having toestablish a new connection from scratch. Where the connection 16 is anRRC connection, for instance, the UE 14 may request resumption of theconnection 16 as part of transmitting from RRC_INACTIVE to RRC_CONNECTEDstate.

The UE 14 can however request that the connection 16 be resumed at atarget RAN node 12-2 (also referred to as a new serving RAN node) thatis the same or different than the source RAN node 12-1 (also referred toas an old serving RAN node) at which the connection 16 was suspended.The UE 14 may do so for instance after the UE moves from one place toanother during suspension of the connection 16. As shown in FIG. 1 inthis regard the UE 14 requests that the connection 16 be resumed at atarget RAN node 12-2 that also connects to the CN 16A of PLMN A. To doso, the UE 14 transmits to the target RAN node 12-2 signalling 24 thatincludes a request 26 to resume the connection 16 (at the target RANnode 12-2). In some embodiments, the request 26 may be referred to asmessage 3 (MSG3) in a random access procedure.

Regardless, in order to resume the connection 16, the target RAN node12-2 needs to be able to locate where the context 18A for the connection16 is stored, either at the target RAN node 12-2 itself or at anotherRAN node. In some embodiments, then, the source RAN node 12-1 forms theresume identifier 22 from an identity of the RAN node storing thecontext 18A for the connection 16. The resume identifier 22 may also beformed from an identity of the UE 14 for which the context 18A isstored, e.g., such that the resume identifier 22 is the concatenation ofthe RAN node identity and the UE identity. The UE 14 correspondinglyincludes the resume identifier 22 in the request 26 to resume theconnection 16, so that the target RAN node 12-2 can use that resumeidentifier 22 to identify and retrieve the context 18A from the sourceRAN node 12-1.

In some embodiments, though, the resume identifier 22 is specific to acertain public land mobile network (PLMN), meaning that the resumeidentifier 22 is unique only within a certain PLMN. It is not globallyunique across multiple PLMNs. This may be for instance due to the RANnode identity (from which the resume identify is formed) beingPLMN-specific. In fact, in some embodiments, the resume identifier 22 isassociated with a RAN node identity that identifies, using a RAN nodeaddressing space shared by different PLMNs, a RAN node which maintainsthe context 18A for the connection 16 while the connection 16 issuspended. That is, different PLMNs re-use the same RAN node identityaddressing space. Effectively, then, different PLMNs have the same setof resume identifiers usable by UEs to resume suspended connections.

This proves particularly meaningful in a scenario where RAN nodes areshared among operators of different PLMNs. Unless the PLMN operatorsdivide or coordinate their usage of resume identifiers, different RANnodes may associate the same resume identifier with different contextsand thereby create ambiguity regarding which context is to be used forresuming a connection.

Consider for instance the scenario shown in FIG. 1 where the target RANnode 12-2 is shared among an operator of PLMN A and an operator of PLMNB. In this case, the target RAN node 12-2 may be connected to not onlythe CN 16A of PLMN A but also to a CN 16B of PLMN B. The target RAN node12-2 may correspondingly have interfaces (e.g., Xn interfaces) to bothRAN nodes used by PLMN A (such as source RAN node 12-1) and RAN nodesused by PLMN B (such as RAN node 12-3). Because the operators of PLMNs Aand B do not divide or coordinate their usage of resume identifiers, thesource RAN node 12-1 for PLMN A and the RAN node 12-3 for PLMN B mayassociate the same resume identifier 22 with the different contexts 18Aand 18B. This may be for instance because the source RAN node 12-1 andthe other RAN node 12-3 are identified using the same RAN node identity.Regardless, this means that the resume identifier 22 itself may notunambiguously indicate to the target RAN node 12-2 from which of the RANnodes 12-1 or 12-3 to retrieve the context 18A for the connection 16that UE 14 requests resumption of.

Some embodiments herein facilitate context retrieval in these and otherscenarios by associating the resume identifier 22 with a PLMN. As shownin FIG. 1, for instance, the UE 14 transmits to the target RAN node 12-2an indication 28-2 of the PLMN with which the resume identifier 22 isassociated, e.g., the PLMN to which the UE 14 connected using theconnection 16, namely PLMN A. The PLMN associated with the resumeidentifier 22 (e.g., as defined according to one or more rules) may befor instance the PLMN with which the UE 14 is registered, the PLMNselected by the UE 14, or the primary PLMN of the cell or primarysynchronization signal (PSS)/secondary synchronization signal (SSS)where the resume identifier 22 was assigned. Regardless of theparticular PLMN, the UE 14 in some embodiments transmit this PLMNindication 28-2 within signalling 24. In one embodiment, the UE 14includes the PLMN indication 28-2 within the resume request 26 itself,along with the resume identifier 22. In another embodiment, the UE 14includes the PLMN indication 28-2 in a separate message from the request26, e.g., in a resume complete message.

No matter how the target RAN node 12-2 receives the resume identifier 22and PLMN indication 28-2 from the UE 14, the target RAN node 12-2retrieves the context 18A for the connection 16 based on that resumeidentifier 22 and PLMN indication 28-2. Even if the RAN nodes 12-1 and12-3 have the same RAN node identity, for instance, the target RAN node12-2 selectively retrieves the context 18A for the connection 16 fromthe source RAN node 12-1 for PLMN A, not from RAN node 12-3 for PLMN B.Indeed, the association of PLMN A with the resume identifier 22 resolvesany ambiguity that might exist regarding which RAN node 12-1 or 12-3stores the context 18A for the connection 16.

In some embodiments, for example, the target RAN node 12-2 identifies,based on the resume identifier 22 and the indication 28-2 of the PLMNwith which the resume identifier 22 is associated, an interface (e.g.,an Xn interface) to a RAN node which maintains the context 18A for theconnection 16. In one embodiment, for instance, the target RAN node 12-2identifies the interface based on a mapping that associates differentcombinations of PLMN indications and resume identifiers (orPLMN-specific RAN node identities from which resume identifiers areformed) with different interfaces. In one example, then, the target RANnode 12-2 identifies the interface to the source RAN node 12-1 as beingthe interface to which is mapped a combination of the indication 28-2 ofPLMN A and a PLMN-specific RAN node identity included in the resumeidentifier 22. Having identified this interface, the target RAN node12-2 then retrieves the context 18A over that identified interface.

In other embodiments, the target RAN node 12-2 may determine, based onthe resume identifier 22 and the indication 28-2 of the PLMN with whichthe resume identifier 22 is associated, that an interface to a RAN nodewhich maintains the context 18A for the connection 16 is not availableat the target RAN node 12-2. That is, the target RAN node 12-2 lacks aninterface (e.g., an Xn interface) to the RAN node which maintains thecontext 18A. In this case, the target RAN node 12-2 may select, based onthe indication 28-2 of the PLMN with which the resume identifier 22 isassociated, a core network node (e.g., a node that implements an accessand mobility function, AMF) that supports the PLMN with which the resumeidentifier 22 is associated (e.g., a node in CN16A for PLMN A). Thetarget RAN node 12-2 may then transmit a request for the context 18A tothe selected core network node. The target RAN node 12-2 may include theresume identifier 22 in the request. With any ambiguity attributable todifferent possible PLMNs having been resolving in this way by the targetRAN node 12-2, the core network node for that PLMN then correspondinglyretrieves the context 18A for the target RAN node 12-2 and forwards itto the target RAN node 12-2.

Some embodiments thereby advantageously enable context transfer in RANsharing scenarios, even without inefficient coordination between PLMNoperators (e.g., in terms of how the PLMN operators use their resumeidentifiers). This in turn proves advantageous in that, in someembodiments, the entire resume identifier remains available forindependent use by each PLMN operator and thereby preserves the numberof resume identifiers available for use by each PLMN operator.Alternatively or additionally, some embodiments enable context transferin RAN sharing scenarios even without negative impact on UE performance.For example, some embodiments avoid unnecessary UE signalling that mightotherwise be required to resolve the ambiguity regarding which RAN nodestores its context. Avoiding this unnecessary UE signalling in turnminimizes UE battery consumption and service delays.

Note that the UE 14 may indicate the PLMN with which the resumeidentifier 22 is associated in any number of ways. In some embodiments,the PLMN indication 28-2 in this regard is a complete PLMN identity(PLMN ID) indicated explicitly in the signalling 24. In otherembodiments, the PLMN indication 28-2 is an index of a specific PLMNidentity in a list of PLMN identities, where each PLMN identity in thelist has an associated index. This list of PLMN identities may bebroadcast by the target RAN node 12-2, e.g., in or as part of systeminformation or other common signalling.

Note further that the source RAN node 12-1 may in some embodiments storean indication 28-1 of the PLMN with which the resume identifier 22 isassociated. The indication 28-1 stored by the source RAN node 12-1 maybe the same as or different from the indication 28-2 used with respectto the target RAN node 12-2, e.g., the indications 28-1 and 28-2 mayindicate the same PLMN but with different indices in an uncoordinatedmanner between the RAN nodes. As shown in FIG. 1 for example, the sourceRAN node 12-1 in some embodiments stores a PLMN indication 28-1 in thecontext 18A or in association with the context 18A (e.g., via the resumeidentifier 22). Alternatively or additionally, the source RAN node 12-1may transmit the PLMN indication 28-1 to the UE 14, e.g., with dedicatedsignalling when the source RAN node 12-1 provides the UE 14 with theresume identifier 22. The source RAN node 12-1 may for instance includethe PLMN indication 28-1 within the suspend message 20 along with theresume identifier 22, as shown in FIG. 1. In some embodiments where theindications 28-1 and 28-2 are different, the UE 14 may be configured totranslate between the indications 28-1 and 28-2 when communicating withthe different RAN nodes 12-1 and 12-2.

Note as well that, when initially creating the context 18A for theconnection 16 (e.g., upon initial establishment of the connection 16),the source RAN node 12-1 in some embodiments stores an indication of thePLMN with which the connection 16 and/or context 18A is associated. Thesource RAN node 12-1 may for instance store such an indication in, or inassociation with, the context 18A itself. Where the PLMN associated withthe connection 16 and/or context 18A is the PLMN with which the UE 14 isregistered, for example, the source RAN node 12-1 may store the UE'sregistered PLMN in the context 18A in connection with initial creationof the context 18A. In these and other embodiments, the UE 14 mayindicate the PLMN with which the requested connection 16 is to beassociated in signalling used to request the initial establishment ofthat connection 16, e.g., within message 3 of a random access procedure.Then, when the connection 16 is later suspended, the source RAN node12-1 in some embodiments uses this stored indication to generate thesuspend message 20 to include the resume identifier 22 and PLMNindication 28-1 indicating the PLMN with which the resume identifier 22is associated. Alternatively or additionally, if the source RAN node12-1 is the target RAN node 12-2 at which the UE 14 requests resumptionof the connection 16, the source RAN node 12-1 may identify the PLMNwith which the resume identifier 22 is associated based on theindication stored in or in association with the context 18A, e.g., suchthat in some embodiments the UE 14 need not include the PLMN indication28-2 in the signalling 24 requesting resumption of the connection 14.

Other embodiments herein avoid or resolve similar ambiguities that mayexist with respect to a UE identifier included in a paging message foridentifying the target UE of the page. Such a paging message may in factbe what triggers the UE 14 in FIG. 1 to request resumption of itsconnection at the target RAN node 12-2.

Regardless, as shown in FIG. 2, a UE 30-1 listens for a paging message32A while the UE 30-1 is in a suspended state or an idle state withrespect to a RAN node 12-4 for PLMN A. In the suspended state, aconnection 34 between the UE 30-1 and RAN node 12-4 is suspended. In theidle state, by contrast, the connection 34 is released. Where theconnection 34 is an RRC connection for instance the suspended state maybe referred to as RRC_INACTIVE and the idle state may be referred to asRRC_IDLE. Regardless, from listening for such a paging message, the UE30-1 as shown receives a paging message 32A that includes a UEidentifier 36 which identifies a target UE of the paging message 32A.

In some embodiments, the UE identifier 36 is specific to a certain PLMN,meaning that the UE identifier 36 is unique only within a certain PLMN.It is not globally unique across multiple PLMNs. For example, in someembodiments, the UE identifier 36 has an addressing space shared bydifferent PLMNs. Effectively, different PLMNs have the same set of UEidentifiers usable for identifying UEs. In fact, particularly inembodiments where the connection 34 corresponds to the connection 16 inFIG. 1 that has been suspended, the paging message 32A may includes theresume identifier 22 discussed above as the UE identifier 36. In thiscase, then, the UE identifier 36 inherits the same ambiguities discussedabove with respect to the resume identifier 22. In this and other cases,then, unless the PLMN operators divide or coordinate their usage of UEidentifiers, different UEs may be identified using the same UEidentifier and thereby create ambiguity regarding which UE is to respondto the paging message 32A. For example, another RAN node 12-5 for PLMN Bas shown in FIG. 2 may identify a different UE 30-2 using the same UEidentifier 36. This means that the UE identifier 36 itself may notunambiguously indicate to the UE 30-1 which UE is the target of thepaging message 32A.

Some embodiments herein facilitate paging in these and other scenariosby associating the UE identifier 36 with a PLMN. As shown in FIG. 2, forinstance, the RAN node 12-4 generates the paging message 32A to includean indication 38-4 of a PLMN associated with the UE identifier 36. TheUE 30-1 determines, based on the UE identifier 36 and the PLMNindication 38-4, whether the UE 30-1 is the target UE of the pagingmessage 32A. By basing this determination on both the UE identifier 36and the PLMN indication 38-4, the UE 30-1 is able to successfullydecipher whether it is the intended target, even if RAN node 12-5 wereto transmit its own paging message 32B to UE 30-2 with the same UEidentifier 36, because that paging message 32B would have an indication38-5 for PLMN B instead. The UE 30-1 thereafter replies or refrains fromreplying to the paging message 32A depending respectively on whether ornot the UE 30-1 is the target UE of the page.

Some embodiments thereby advantageously enable paging in RAN sharing andother scenarios, even without inefficient coordination between PLMNoperators (e.g., in terms of how the PLMN operators use their UEidentifiers). This in turn proves advantageous in that, in someembodiments, the entire UE identifier remains available for independentuse by each PLMN operator and thereby preserves the number of UEidentifiers available for use by each PLMN operator. Alternatively oradditionally, some embodiments enable paging in RAN sharing and otherscenarios even without negative impact on UE performance. For example,some embodiments avoid unnecessary UE signalling that might otherwise berequired to resolve the ambiguity regarding which UE is the intendedtarget of a page. Avoiding this unnecessary UE signalling in turnminimizes UE battery consumption and service delays.

Note that in some embodiments the RAN node 12-4 receives the pagingmessage 32A from another RAN node (e.g., a source RAN node that stores acontext for the UE 30-1) or from a core network node in CN 16A (e.g., acore network node via which paging of the UE 30-1 is relayed). In someembodiments, for instance, the paging message 32A a core network node inthe form of a node that implements an access and mobility function(AMF). Embodiments herein thereby further include a RAN node or corenetwork node generating and/or transmitting paging message 32A to RANnode 12-4, where that paging message 32A includes UE ID 36 as well asPLMN indication 38-4.

Note also that the PLMN indication 38-4 in FIG. 2 may indicate the PLMNassociated with the UE identifier 36 in any of the ways described abovewith respect to the PLMN indication 28-1 and 28-2 in FIG. 1.

Note also that, in some embodiments, different RAN nodes or cells mayindicate the same PLMN with different indications, e.g., in anuncoordinated manner. For example, one RAN node or cell may indicate thePLMN associated with the UE's connection (e.g., the UE's registeredPLMN) using an index of 5 (with reference to the list of PLMNsbroadcasted by the RAN node or in the cell). Another RAN node or cellhowever may indicate the same PLMN using an index of 3. In someembodiments, then, a UE stores or otherwise tracks which indications(e.g., indices) correspond to the PLMN associated with the UE'sconnection in different RAN nodes or cells. For example, the UE maystore the full PLMN ID of that PLMN as well as information indicatingthat the full PLMN ID corresponds to different indices in different RANnodes or cells.

In these and other embodiments, then, the source RAN node 12-1 in FIG. 1may use a different index to PLMN mapping than the target RAN node 12-2.For example, the source RAN node 12-1 may include index 5 as the PLMNindication 28-1 in the suspend message 20 to the UE 14, where index 5 atthe source RAN node 12-1 is mapped to PLMN A. The target RAN node 12-2however maps index 3 to PLMN A. With knowledge of this, the UE 14 mayinstead use index 3 as the PLMN indication 28-2 in the signalling 24 tothe target RAN node 12-2 to resume the connection. Similarly, where thetarget RAN node 12-2 pages the UE during the suspended connection (suchthat the target RAN node 12-2 is the RAN node 12-4 in FIG. 2), the UE 14may receive a paging message 32A with index 3 as the PLMN indication38-4.

Although embodiments herein have been described with respect to an RRCconnection, embodiments herein are extendable to other types ofconnections. Some embodiments for example extend to any type of controlplane connection or signalling connection between the wireless device 14and the radio network node 12.

In view of the above modifications and variations, FIG. 3 shows a method100 performed by a user equipment 14 according to some embodiments. Asshown, the method 100 comprises receiving at the user equipment 14, froma source RAN node 12-1 with which the user equipment 14 has a connection16, a message 20 indicating that the connection 16 is to be suspendedand indicating a resume identifier 22 usable by the user equipment 14 toresume the connection 16 after the connection 16 is suspended (Block110). In some embodiments, the resume identifier 22 is associated with aRAN node identity that identifies, using a RAN node addressing spaceshared by different PLMNs, a RAN node which maintains a context 18A forthe connection 16 while the connection 16 is suspended. Alternatively oradditionally, different PLMNs in some embodiments have the same set ofresume identifiers usable by user equipments to resume suspendedconnections.

Regardless, the method 100 as shown also includes, while the connection16 is suspended, transmitting from the user equipment 14 to a target RANnode 12-2 a request 26 to resume the connection 16 (Block 120). Therequest 26 includes the resume identifier 22. The method 100 furtherincludes transmitting from the user equipment 14 to the target RAN node12-2 an indication 28-2 of a PLMN with which the resume identifier 22 isassociated (Block 130). For example, the user equipment 14 may transmitthe indication 28-2 within the request 26 or within a separate message.In some embodiments, the indication 28-2 of a PLMN with which the resumeidentifier 22 is associated is an indication of a PLMN with which theuser equipment 14 is registered or an indication of a PLMN selected bythe user equipment 14. Regardless, in some embodiments, the userequipment 14 transmits the request 26 and/or the indication 28-2responsive to receiving a paging message 32A that includes the resumeidentifier 22 and an indication 28-4 of the PLMN associated with theresume identifier 22 (Block 115). As discussed above, this indication28-4 may be the same or different than the indication 28-2 but bothindications 28-2 and 28-4 indicate the same PLMN; namely, the PLMNassociated with the resume identifier 22 or UE identifier.

The indication 28-2 of the PLMN with which the resume identifier 22 isassociated in some embodiments is a complete PLMN identity (PLMN ID). Inother embodiments, the method 100 includes receiving (e.g., in systeminformation) a list of PLMN identities that are each associated with anindex (Block 105). In this case, the indication 28-2 may be an index ofa specific PLMN identity in the list of PLMN identities.

Although not shown, the method 100 may also include, before transmittingthe request 26 to resume the connection 16, receiving from the sourceRAN node 12-1 a message 20 indicating that the connection 16 is to besuspended and indicating the resume identifier 22 usable by the userequipment 14 to resume the connection 16 after the connection 16 issuspended. The method 100 may further comprise receiving from the sourceRAN node 12-1 an indication 28-1 of the PLMN with which the resumeidentifier 22 is associated. The indication 28-1 may for instance beincluded in the message 20. Also as discussed above, this indication28-1 may be the same or different than the indication 28-2 but bothindications 28-1 and 28-2 indicate the same PLMN; namely, the PLMNassociated with the resume identifier 22.

Note that in some embodiments, transmission of the request to resume theconnection 16 may be conditional on the PLMN with which the resumeidentifier 22 is associated being available and/or the UE's registeredPLMN being available. When the PLMN with which the resume identifier 22is associated is not available and/or the UE's registered PLMN is notavailable, the method 100 may instead comprise leaving a suspended statein which the connection 16 is suspended and/or going to an idle state inwhich the connection 16 is released. The method 100 in some embodimentsmay then include requesting establishment of a new connection (e.g., anew RRC connection).

FIG. 4 illustrates a method 200 performed by a RAN node configured tooperate as a target RAN node according to some embodiments. The method200 comprises receiving at the target RAN node 12-1 a request 26 from auser equipment 14 to resume a connection 16 that was suspended betweenthe user equipment 14 and a source RAN node 12-1 (Block 210). Therequest 26 includes a resume identifier 22. In some embodiments, theresume identifier 22 is associated with a RAN node identity thatidentifies, using a RAN node addressing space shared by different PLMNs,a RAN node which maintains a context 18A for the connection 16 while theconnection 16 is suspended. Alternatively or additionally, differentPLMNs in some embodiments have the same set of resume identifiers usableby user equipments to resume suspended connections.

Regardless, the method 200 as shown also includes receiving at thetarget RAN node 12-1, from the user equipment 14, an indication 28-2 ofa PLMN with which the resume identifier 22 is associated (Block 220).For example, the target RAN node 12-1 may receive the indication 28-2within the request 26 or within a separate message. In some embodiments,the indication 28-2 of a PLMN with which the resume identifier 22 isassociated is an indication of a PLMN with which the user equipment 14is registered or an indication of a PLMN selected by the user equipment14. Regardless, in some embodiments, the target RAN node 12-2 receivesthe request 26 and/or the indication 28-2 responsive to transmitting apaging message 32A that includes the resume identifier 22 and theindication 28-2 of the PLMN associated with the resume identifier 22(Block 206).

The indication 28-2 of the PLMN with which the resume identifier 22 isassociated in some embodiments is a complete PLMN identity (PLMN ID). Inother embodiments, the method 200 includes transmitting (e.g., in systeminformation) a list of PLMN identities that are each associated with anindex (Block 202). In this case, the indication 28-2 may be an index ofa specific PLMN identity in the list of PLMN identities.

In any event, the method 200 as shown further includes retrieving by thetarget RAN node 12-2 a context 18A for the connection 16, based on theresume identifier 22 and the indication 28-2 of the PLMN with which theresume identifier 22 is associated (Block 230). In some embodiments, forexample, such retrieval comprises identifying, based on the resumeidentifier 22 and the indication 28-2 of the PLMN with which the resumeidentifier 22 is associated, an interface to a RAN node which maintainsthe context 18A for the connection 16. In this case, the target RAN node12-2 retrieves, over the identified interface, the context 18A for theconnection 16.

In other embodiments, such retrieval comprises determining, based on theresume identifier 22 and the indication 28-2 of the PLMN with which theresume identifier 22 is associated, that an interface to a RAN nodewhich maintains the context 18A for the connection 16 is not availableat the target RAN node 12-2. In this case, retrieval may entailselecting, based on the indication 28-2 of the PLMN with which theresume identifier 22 is associated, a core network node that supportsthe PLMN with which the resume identifier 22 is associated. Retrievalmay then involve transmitting a request for the context 18A to theselected core network node. This request includes the resume identifier22.

FIG. 5 illustrates a method 300 performed by a RAN node configured tooperate as a source RAN node 12-1 according to some embodiments. Asshown, the method 300 comprises establishing a connection 16 between thesource RAN node 12-1 and a user equipment 14 (Block 310). The method 300also comprises transmitting from the source RAN node 12-1 a message 20to the user equipment 14 indicating that the connection 16 is to besuspended and indicating a resume identifier 22 usable by the userequipment 14 to resume the connection 16 after the connection 16 issuspended (Block 320). The method 300 further comprises transmittingfrom the source RAN node 12-1 to the user equipment 14 an indication28-1 of a PLMN with which the resume identifier 22 is associated (Block330). The indication 28-1 may for instance be included in the message20. In some embodiments, the indication 28-1 of a PLMN with which theresume identifier 22 is associated is an indication of a PLMN with whichthe user equipment 14 is registered or an indication of a PLMN selectedby the user equipment 14.

The indication 28-1 of the PLMN with which the resume identifier 22 isassociated in some embodiments is a complete PLMN identity (PLMN ID). Inother embodiments not shown, the method 300 includes transmitting (e.g.,in system information) a list of PLMN identities that are eachassociated with an index. In this case, the indication 28-1 may be anindex of a specific PLMN identity in the list of PLMN identities.

In some embodiments, the method 300 further comprises storing a context18A for the connection 16, e.g., even while the connection 16 issuspended (Block 340). The method 300 may further comprise storing inthe context 18A, or in association with the context 18A, the indication28-1 of the PLMN with which the resume identifier 22 is associated(Block 350).

FIG. 6 illustrates a method 400 performed by a RAN node 12-4 accordingto still other embodiments. As shown, the method 400 includestransmitting a paging message 32A that includes a user equipmentidentifier 36 and an indication 38-4 of a PLMN associated with the userequipment identifier 36 (Block 410). The paging message 32A may forinstance be transmitted over a radio interface to the user equipment towhich the paging message 32A is directed. Or, the paging message 32A maybe transmitted to another RAN node or a core network node via which thepaging message 32A is to be relayed, for forwarding to the userequipment.

In some embodiments, the RAN node 12-4 transmits the paging message 32Awhile a connection 16 with the user equipment to which the pagingmessage 32A is directed is in a suspended state. In this case, the userequipment identifier 36 may be the resume identifier 22 discussed above,such that the indication 38-4 is an indication 28-1 or 28-2 of a PLMNwith which the resume identifier 22 is associated. In this case, the RANnode 12-4 may be the same as the target RAN node 12-2 or the source RANnode 12-1 in FIG. 1.

In some embodiments, the indication 38-4 of a PLMN with which the userequipment identifier 36 is associated is an indication of a PLMN withwhich the user equipment 30-1 is registered or an indication of a PLMNselected by the user equipment 30-1. In any event, the indication 38-4of the PLMN with which the user equipment identifier 36 is associated insome embodiments is a complete PLMN identity (PLMN ID). In otherembodiments, the method 400 includes transmitting (e.g., in systeminformation) a list of PLMN identities that are each associated with anindex (Block 402). In this case, the indication 38-4 may be an index ofa specific PLMN identity in the list of PLMN identities.

FIG. 6 also shows that in some embodiments the method 400 may includeobtaining (e.g., receiving or generating) the paging message 32A (Block406). In one embodiment for instance the RAN node 12-4 itself generatesthe paging message 32A. In other embodiments, the RAN node 12-4 receivesthe paging message 32A from another RAN node (e.g., that stores thecontext 18A for the connection 16) or from a core network node (e.g., anode implementing an AMF) such as a core network node via which pagingis relayed.

FIG. 7 shows a method 500 performed by a user equipment 30-1 accordingto some embodiments. As shown, the method 500 includes listening for apaging message 32A while the user equipment 30-1 is in a suspended stateor an idle state (Block 510). In the suspended state, a connection 34between the user equipment 30-1 and RAN node 12-4 is suspended. In theidle state, by contrast, the connection 34 is released. Where theconnection 34 is an RRC connection for instance the suspended state maybe referred to as RRC_INACTIVE and the idle state may be referred to asRRC_IDLE. Regardless, from listening for such a paging message, themethod 500 as shown further includes receiving a paging message 32A thatincludes a user equipment identifier 36 which identifies a target UE ofthe paging message 32A and that includes an indication 38-4 of a PLMNassociated with the user equipment identifier 36 (Block 520).

In some embodiments, the user equipment 30-1 receives the paging message32A while a connection 16 between a RAN node 14-4 and the user equipment30-1 is in a suspended state. In this case, the user equipmentidentifier 36 may be the resume identifier 22 discussed above, such thatthe indication 38-4 is an indication 28-1 or 28-2 of a PLMN with whichthe resume identifier 22 is associated. In this case, the RAN node 12-4may be the same as the target RAN node 12-2 or the source RAN node 12-1in FIG. 1.

In some embodiments, the indication 38-4 of a PLMN with which the userequipment identifier 36 is associated is an indication of a PLMN withwhich the user equipment 30-1 is registered or an indication of a PLMNselected by the user equipment 30-1. In any event, the indication 38-4of the PLMN with which the user equipment identifier 36 is associated insome embodiments is a complete PLMN identity (PLMN ID). In otherembodiments, the method 500 includes receiving (e.g., in systeminformation) a list of PLMN identities that are each associated with anindex (Block 505). In this case, the indication 38-4 may be an index ofa specific PLMN identity in the list of PLMN identities.

In some embodiments, the UE identifier 36 is specific to a certain PLMN,meaning that the UE identifier 36 is unique only within a certain PLMN.It is not globally unique across multiple PLMNs. For example, in someembodiments, the UE identifier 36 has an addressing space shared bydifferent PLMNs. Effectively, then, different PLMNs in these embodimentshave the same set of UE identifiers usable for identifying UEs.

Regardless, the method 500 as shown in some embodiments further includesdetermining, based on the user equipment identifier 36 and theindication 38-4 of the PLMN associated with the user equipmentidentifier 36, whether the user equipment 30-1 is the target userequipment of the paging message 32A (Block 530). In this case, themethod may further comprise replying or refraining from replying to thepaging message 32A depending respectively on whether or not the userequipment is the target user equipment (Block 540).

Note that the user equipment 14 or 30-1 described above may perform themethods herein and any other processing by implementing any functionalmeans, modules, units, or circuitry. In one embodiment, for example, theuser equipment 14 or 30-1 comprises respective circuits or circuitryconfigured to perform the steps shown in FIGS. 3 and/or 7. The circuitsor circuitry in this regard may comprise circuits dedicated toperforming certain functional processing and/or one or moremicroprocessors in conjunction with memory. For instance, the circuitrymay include one or more microprocessor or microcontrollers, as well asother digital hardware, which may include digital signal processors(DSPs), special-purpose digital logic, and the like. The processingcircuitry may be configured to execute program code stored in memory,which may include one or several types of memory such as read-onlymemory (ROM), random-access memory, cache memory, flash memory devices,optical storage devices, etc. Program code stored in memory may includeprogram instructions for executing one or more telecommunications and/ordata communications protocols as well as instructions for carrying outone or more of the techniques described herein, in several embodiments.In embodiments that employ memory, the memory stores program code that,when executed by the one or more processors, carries out the techniquesdescribed herein.

FIG. 8A for example illustrates a user equipment 600 as implemented inaccordance with one or more embodiments. The user equipment 600 may beUE 14 in FIG. 1 or UE 30-1 in FIG. 2. As shown, the user equipment 600includes processing circuitry 610 and communication circuitry 620. Thecommunication circuitry 620 (e.g., radio circuitry) is configured totransmit and/or receive information to and/or from one or more othernodes, e.g., via any communication technology. Such communication mayoccur via one or more antennas that are either internal or external tothe user equipment 600. The processing circuitry 610 is configured toperform processing described above (e.g., in FIGS. 3 and/or 7), such asby executing instructions stored in memory 630. The processing circuitry610 in this regard may implement certain functional means, units, ormodules.

FIG. 8B illustrates a schematic block diagram of a user equipment 700according to still other embodiments. The user equipment 700 may be forinstance the UE 14 in FIG. 1. As shown, the user equipment 700implements various functional means, units, or modules, e.g., via theprocessing circuitry 610 in FIG. 8A and/or via software code. Thesefunctional means, units, or modules, e.g., for implementing the method100 in FIG. 3, include for instance a receiving unit 710 for receivingat the user equipment 700, from a source RAN node 12-1 with which theuser equipment 700 has a connection 16, a message 20 indicating that theconnection 16 is to be suspended and indicating a resume identifier 22usable by the user equipment 700 to resume the connection 16 after theconnection 16 is suspended. Also included is a transmitting unit 720for, while the connection 16 is suspended, transmitting from the userequipment 700 to a target RAN node 12-2 a request 26 to resume theconnection 16. The request 26 includes the resume identifier 22. Thetransmitting unit 720 may also be for transmitting from the userequipment 700 to the target RAN node 12-2 an indication 28-2 of a PLMNwith which the resume identifier 22 is associated.

FIG. 8C illustrates a schematic block diagram of a user equipment 800according to still other embodiments. The user equipment 800 may be forinstance the UE 30-1 in FIG. 2. As shown, the user equipment 800implements various functional means, units, or modules, e.g., via theprocessing circuitry 610 in FIG. 8A and/or via software code. Thesefunctional means, units, or modules, e.g., for implementing the method500 in FIG. 7, include for instance a listening unit 810 for listeningfor a paging message 32A while the user equipment 800 is in a suspendedstate or an idle state. Also included may be a receiving unit 820 for,from listening for such a paging message, receiving a paging message 32Athat includes a user equipment identifier 36 which identifies a targetUE of the paging message 32A and that includes an indication 38-4 of aPLMN associated with the user equipment identifier 36.

Note also that the RAN node 12-1, 12-2, or 12-4 described above mayperform the methods herein and any other processing by implementing anyfunctional means, modules, units, or circuitry. In one embodiment, forexample, the RAN node 12-1, 12-2, or 12-4 comprises respective circuitsor circuitry configured to perform the steps shown in FIGS. 4, 5, and/or6. The circuits or circuitry in this regard may comprise circuitsdedicated to performing certain functional processing and/or one or moremicroprocessors in conjunction with memory. For instance, the circuitrymay include one or more microprocessor or microcontrollers, as well asother digital hardware, which may include digital signal processors(DSPs), special-purpose digital logic, and the like. The processingcircuitry may be configured to execute program code stored in memory,which may include one or several types of memory such as read-onlymemory (ROM), random-access memory, cache memory, flash memory devices,optical storage devices, etc. Program code stored in memory may includeprogram instructions for executing one or more telecommunications and/ordata communications protocols as well as instructions for carrying outone or more of the techniques described herein, in several embodiments.In embodiments that employ memory, the memory stores program code that,when executed by the one or more processors, carries out the techniquesdescribed herein.

FIG. 9A more particularly illustrates a RAN node 900 as implemented inaccordance with one or more embodiments. The RAN node 900 may be the RANnode 12-1, 12-2, or 12-4 as described above. As shown, the RAN node 900includes processing circuitry 910 and communication circuitry 920. Thecommunication circuitry 920 is configured to transmit and/or receiveinformation to and/or from one or more other nodes, e.g., via anycommunication technology. The processing circuitry 910 is configured toperform processing described above (e.g., in FIGS. 4, 5, and/or 6), suchas by executing instructions stored in memory 930. The processingcircuitry 910 in this regard may implement certain functional means,units, or modules.

FIG. 9B for example illustrates a schematic block diagram of a RAN node1000 according to still other embodiments. The RAN node 1000 may be forinstance target RAN node 12-2 in FIG. 1. As shown, the RAN node 1000implements various functional means, units, or modules, e.g., via theprocessing circuitry 910 in FIG. 9A and/or via software code. Thesefunctional means, units, or modules, e.g., for implementing the methodin FIG. 4, include for instance a receiving unit 1010 for receiving atthe RAN node 1000 a request 26 from a user equipment 14 to resume aconnection 16 that was suspended between the user equipment 14 and asource RAN node 12-1. The request 26 includes a resume identifier 22.The receiving unit 1010 may also be for receiving at the RAN node 1000,from the user equipment 14, an indication 28-2 of a PLMN with which theresume identifier 22 is associated. Also included may be a retrievingunit 1020 for retrieving by the RAN node 1000 a context 18A for theconnection 16, based on the resume identifier 22 and the indication 28-2of the PLMN with which the resume identifier 22 is associated.

FIG. 9C illustrates a schematic block diagram of a RAN node 1100according to yet other embodiments. The RAN node 1100 may be forinstance source RAN node 12-1 in FIG. 1. As shown, the RAN node 1100implements various functional means, units, or modules, e.g., via theprocessing circuitry 910 in FIG. 9A and/or via software code. Thesefunctional means, units, or modules, e.g., for implementing the methodin FIG. 5, include for instance an establishing unit 1110 forestablishing a connection 16 between the RAN node 1100 and a userequipment 14. Also included is a transmitting unit 1120 for transmittingfrom the RAN node 1100 a message 20 to the user equipment 14 indicatingthat the connection 16 is to be suspended and indicating a resumeidentifier 22 usable by the user equipment 14 to resume the connection16 after the connection 16 is suspended. The transmitting unit 1120 mayalso be for transmitting from the RAN node 1100 to the user equipment 14an indication 28-1 of a PLMN with which the resume identifier 22 isassociated.

FIG. 9D illustrates a schematic block diagram of a RAN node 1200according to other embodiments. The RAN node 1200 may be for instanceRAN node 12-4 in FIG. 2. As shown, the RAN node 1200 implements variousfunctional means, units, or modules, e.g., via the processing circuitry910 in FIG. 9A and/or via software code. These functional means, units,or modules, e.g., for implementing the method in FIG. 6, include forinstance a transmitting unit 1220 for transmitting a paging message 32Athat includes a user equipment identifier 36 and an indication 38-4 of aPLMN associated with the user equipment identifier 36. Also included maybe an obtaining unit 1210 for obtaining (e.g., generating or receiving)the paging message 32A.

Those skilled in the art will also appreciate that embodiments hereinfurther include corresponding computer programs.

For example, embodiments herein include a computer program thatcomprises instructions which, when executed on at least one processor ofa user equipment 14 or 30-1, cause the user equipment 14 or 30-1 tocarry out any of the respective processing described above. A computerprogram in this regard may comprise one or more code modulescorresponding to the means or units described above.

Other embodiments herein include a computer program that comprisesinstructions which, when executed on at least one processor of a RANnode 12-1, 12-2, or 12-4, cause the RAN node 12-1, 12-2, or 12-4 tocarry out any of the respective processing described above. A computerprogram in this regard may comprise one or more code modulescorresponding to the means or units described above.

Embodiments further include a carrier containing any of these computerprograms. This carrier may comprise one of an electronic signal, opticalsignal, radio signal, or computer readable storage medium.

In this regard, embodiments herein also include a non-transitorycomputer readable (storage or recording) medium comprising instructionsthat, when executed by a processor of user equipment 14 or 30-1, causethe user equipment 14 or 30-1 to perform as described above. Embodimentsfurther include a non-transitory computer readable (storage orrecording) medium comprising instructions that, when executed by aprocessor of RAN node 12-1, 12-2, or 12-4 cause the RAN node 12-1, 12-2,or 12-4 to perform as described above.

Additional embodiments will now be described. At least some of theseembodiments may be described as applicable in certain contexts and/orwireless network types for illustrative purposes, but the embodimentsare similarly applicable in other contexts and/or wireless network typesnot explicitly described.

In the context of the 5G specification effort, 3GPP decided to introducea new RRC Inactive state. The state has, among others, the followingproperties. First, the UE Context is stored in the RAN. This UE Contextis used at subsequent RRC_INACTIVE to RRC_CONNECTED transition. Thestored UE context may include information about UE security context,data radio bearers, connected slices, UE capabilities etc. Second, theRRC Inactive state implicates a RAN paging procedure. In this procedure,the RAN node that the UE was last connected to pages the UE over an areaconsisting of one or more cells, supported by one or more RAN nodes.

The UE Context can be stored in a RAN node serving the UE before/at thetransition from RRC_CONNECTED to RRC_INACTIVE state. This RRC Connectedto RRC Inactive transition is shown in FIG. 10, which is reproduced fromFIG. 4.8.x1-1 in a change request (CR) to 3GPP TS 23.502.

The Connection Suspend procedure is used by the network to suspend theRRC connection and perform a RRC Connected to RRC Inactive statetransition if the UE and the network support RRC Inactive state (see TS38.300 and TS 38.413).

In Step 1, the RAN sends to the UE an RRC message with a Resume ID. TheRAN initiates the transition to the RRC Inactive state (see TS 38.300)providing the UE with its Resume ID. UE remains in CM-CONNECTED state.The N2AP association as well as N3 user plane resources are keptestablished. Data related to the N2AP association, UE Context and N3user plane resources, necessary to resume the connection is kept in theRAN.

In Step 2, the RAN sends to the AMF an N2 Notification (Inactive). TheRAN in this regard notifies the AMF that the UE's RRC state is moved toRRC Inactive state. The N2AP association as well as N3 user planeresources are kept established. Data related to the N2AP association, UEContext and N3 user plane resources is kept in the AMF. AMF stateremains CM-CONNECTED.

In step 1 above, the RAN provides the UE with a UE RAN identity referredto in this document as a Resume ID. This identifier is associated withthe UE Context of that UE stored in RAN.

At a subsequent transition from RRC_INACTIVE to RRC_CONNECTED state, theUE presents the Resume ID to the RAN. The RAN uses the Resume ID tolocate and access the UE Context stored in step 1.

As described in a CR to 3GPP TS 23.502, the Connection Resume procedureis used by the UE to resume the RRC connection and to perform RRCInactive to RRC Connected state transition. This procedure may be usedif the UE and the network support RRC Inactive state (see TS 38.300) andthe UE has stored the necessary information to conduct the ConnectionResume procedure (see TS 38.413) otherwise the Service Request procedureis used, see clause 4.2.3.2 of 3GPP TS 23.502.

FIG. 11 shows the RRC Inactive to RRC Connected state transition, e.g.,as described in FIG. 4.8.x2-1 in a CR to 3GPP TS 23.502. In Step 1, theUE sends to the RAN an RRC message (Resume ID). The UE in this regardinitiates the transition from RRC Inactive state to RRC Connected state,see TS 38.300. The UE provides its Resume ID needed by the RAN to accessthe UE's stored Context.

In Step 2, which is conditional, the RAN performs UE Context Retrieval.UE Context Retrieval is performed when the UE Context associated withthe UE attempting to resume its connection is not locally available atthe accessed RAN. The UE Context Retrieval procedure via radio accessnetwork is specified in TS 38.423. The UE Context Retrieval procedurevia the core network is specified in sub-clause x.y.z and in TS 38.413.

In Step 3, the RAN sends to the UE an RRC message with the Resume ID.The RAN in this regard confirms to the UE that the UE has entered RRCConnected state.

In Step 4,the RAN sends to the AMF an N2 Notification (Connected) TheRAN in this regard notifies the AMF that the UE entered RRC Connectedstate.

As outlined in step 1, the RAN uses the Resume ID to locate and accessthe UE Context. Given a subsequent RRC_INACTIVE to RRC_CONNECTEDtransition attempted by the UE can occur at a different RAN than wasserving the UE at previous RRC_CONNECTED to RRC_INACTIVE transition, theUE Context can be stored at a different RAN than the RAN node accessedby the UE. This is described in step 2. If the new_RAN is different fromthe old_RAN where the UE has entered RRC_INACTIVE state and thus wherethe UE Context is stored, there is a need to locate the old RAN to beable to retrieve the UE Context so that it can be accessed and used bythe new_RAN.

To enable the location of the Resume ID, the Resume ID contains anidentifier allowing the new_RAN to locate the old_RAN.

For completeness, procedures to retrieve the UE Context via RAN and via5G CN are included in FIGS. 12 and 13 respectively.

As shown in FIG. 12, the UE Context Retrieval via the radio accessnetwork procedure is used if the UE in RRC Inactive state requests toresume a connection toward a new RAN while the UE Context is stored atOld Serving RAN, and the UE Context can be retrieved from the OldServing RAN node by means of Xn signalling (only).

In Step 1, the New Serving RAN node retrieves the UE Context from theOld Serving RAN by using the Xn Retrieve UE Context procedure. If theOld Serving RAN node is able to resolve the Resume ID, it provides UEContext data to the New Serving RAN node.

In Step 2, the New Serving RAN performs the N2 Path Switch proceduretowards the AMF.

In Step 3, the New Serving RAN node requests the Old Serving RAN node torelease the UE Context. This message contains Downlink forwardingaddresses for the user data buffered at Old Serving RAN nodes.

In Step 4, the Old Serving RAN forwards to the New Serving RAN pendingDL user data.

As shown in FIG. 13, the UE Context Retrieval via the 5GC procedure isused if the UE in RRC Inactive state requests to resume a connectiontoward a new RAN while the UE Context is stored at Old Serving RAN, andthe UE Context can not be retrieved from the Old Serving RAN node due tolack of Xn interface between the New and the Old Servin RAN node.

In Step 1, the New Serving RAN node realises that it has no Xnconnection to a RAN node with the identity indicated in the Resume IDand decides to perform the Context Retrieval via Core Network procedure.In Step 2, the RAN sends to the AMF an N2 Retrieve UE Context Request(Old RAN ID (contained in the Resume ID), Resume ID, new RAN ID). TheRAN in this regard requests an AMF within a pool to which it isconnected, to resolve the RAN node identity. This AMF node doesn'tnecessarily need to be the AMF serving the UE. Respective signalling isperformed in a connection-less and the AMF stateless manner. If the AMFis able to resolve the address of the indicated Old RAN ID, it forwardsthe request to that node.

In Step 3, the AMF sends to the Old Serving RAN a Retrieve UE ContextRequest (Old RAN ID, New RAN ID, Resume ID). The AMF forward the requestto the Old Serving RAN.

In Step 4, the Old Serving RAN sends to the AMF a Retrieve UE ContextResponse (Old RAN ID, New RAN ID, Resume ID, UE Context). The OldServing RAN node provides UE Context Data.

In Step 5, the AMF sends to the RAN an N2 Retrieve UE Context Response(Resume ID, UE Context). The AMF forwards the information received instep 4 to the New Serving RAN.

In Step 6, the RAN performs with respect to the AMF an N2 Path Switch(no Xn indicator, DL forwarding address). The New Serving RAN nodetriggers the path switch procedure as if it would have received UEcontext data via Xn interface and indicates to the AMF that no Xnconnection is available towards the Old Serving RAN node. The messagealso contains the DL forwarding addresses.

In Step 7, the AMF performs with respect to the Old Serving RAN an N2 UEContext Release. The AMF node performs the N2 UE Context Releaseprocedure (as the New Serving RAN node is not able to trigger it via Xn)and provides the DL forwarding addresses for the user plane data.

In Step 8, if necessary, forwarding of user data takes place.

FIG. 14 shows the RAN Paging Relay via the 5GC procedure used by RAN topage a UE in RRC Inactive state over RAN nodes being in UE'sRegistration Area, e.g. including the RAN nodes towards which theServing RAN node has no Xn interfaces established.

In Step 1, the serving RAN node decides to relay the paging via the 5GC.

In Step 2, the Serving RAN sends to the AMF an N2 Relay Paging Request(N2 Paging, Registration Area). The serving RAN node requests theserving AMF to relay the paging message to the RAN nodes in UE'sRegistration Area.

In Step 3, the AMF, based on received UE's Registration Area, selectsthe RAN nodes to which the paging message will be relayed. The AMF willnot trigger paging repetition on its own.

In Step 4, the AMF sends to the RAN N2 Paging. The AMF in this regardrelays Paging to the RAN nodes in UE's Registration Area.

It is agreed by 3GPP that a UE in RRC_INACTIVE state can be paged by theRAN using a UE RAN identifier. It is assumed that it will be the sameidentifier as used for the location of the UE Context, i.e. UE's ResumeID.

But there currently exists certain challenge(s). The Resume ID isassumed to consist of the: (i) RAN node identity where the UE Context isstored; and (ii) the UE identity in the RAN node where the UE Context isstored. That is, Resume ID:<RAN node id><UE id>.

Accordingly, the RAN node identity is currently unique in a given PLMN,i.e. different PLMNs re-use the same addressing space. In a RAN Sharingscenario, though, the RAN nodes are shared among different operatorshaving their own CN and their own PLMN identities. The latter arebroadcast by RAN in the system information. The RAN identity used forthe shared RAN nodes need to be unique for both operators to avoid anyconfusion in the addressing of the shared RAN node. To achieve this aglobally unique RAN identity can be used consisting of (i) PLMNidentity; (ii) RAN node identity, so as to form a globally unique RANnode identity:<PLMN id><RAN node id>.

The problem is that since the Resume ID only uses the PLMN-specific RANnode id there is a risk for ambiguity in scenarios where the operatorsare sharing part of their network.

For example, two different UEs could be connected to two different PLMNsin two different RAN nodes which use the same RAN node ID. These RANnodes may then allocate the same Resume ID (Resume ID A) to thedifferent UEs since they both use the same RAN node id. If these twoPLMNs are sharing a RAN node which one of the UEs enter and use theResume ID it will not be possible for that RAN node to resolve which RANnode in which PLMN the UE context is located.

A similar problem could occur when paging a UE. In case the UE has beenassigned a Tracking Area list which spans both the shared part of thePLMN and non-shared part. In this case, if the network pages the UE withthe Resume ID assigned in the non-shared part, it is possible that thewrong UE will respond to the message since the Resume IDs could bereused by the different operator.

Certain aspects of the present disclosure and their embodiments mayprovide solutions to these or other challenges.

Some solutions described herein are based on the following principles:

-   -   1. Introduction of a PLMN-specific RAN node identity in the RAN        nodes participating in a RAN Sharing scenario. Each operator can        configure the RAN identity, e.g. by means of operation and        maintenance (O&M) without the need to coordinate it with other        operators sharing the RAN.    -   2. RAN nodes exchanging their PLMN-specific RAN node identities        when establishing their inter RAN node interfaces, i.e. Xn        interfaces.    -   3. RAN node constructing a UE's Resume ID based on the RAN node        identity that is specific to UE's registered PLMN.    -   4. At RRC_CONNECTED to RRC_INACTIVE transition ((see FIG. 10)        the UE is provided by the RAN with a Resume ID that carries a        PLMN-specific RAN node identity of the PLMN that the UE is        registered with.    -   5. At RRC_CONNECTED to RRC_INACTIVE transition, the UE        associates the Resume ID received from the RAN with its        registered PLMN identity.    -   6. At RRC_INACTIVE to RRC_CONNECTED transition ((see FIG. 11)        the UE sends to the RAN: (i) its registered PLMN; and (ii) the        Resume ID received from the node the UE was last connected to.        The coding of the registered PLMN information element could        either be the full PLMN ID or it could be an index value        indicating a specific PLMN on a PLMN list that the cell which        the UE is connecting to has provided to the UE (E.g. via        broadcast channel). Other coding are also possible.    -   7. The New_RAN node locates the old_RAN node based on the        indication of the registered or selected PLMN and the PLMN        specific RAN identity received from the UE's Resume ID. In some        embodiments, location of the old_RAN node is based on the        knowledge of the PLMN specific RAN node identity being        associated with an inter RAN node interface, i.e. Xn interface.        Or, in other embodiments, if the identity is not available on        any Xn interface, the new_RAN will trigger a UE Context        retrieval procedure as shown in FIG. 13 including selecting a CN        node (AMF) that supports the UE's registered/selected PLMN.

Based on these, various embodiments are disclosed, including, but notlimited to a UE (and corresponding method) resuming a connection in atarget cell, providing the network with a resume identifier andindication of registered PLMN (or selected PLMN). Additional embodimentsinclude a UE (and corresponding method) listening for paging in asuspended or idle state. The paging message consists of an indication ofa PLMN and UE identifier (e.g. resume ID) associated with that PLMN.Additional embodiments include associated network nodes andcorresponding methods.

There are, proposed herein, various embodiments which address one ormore of the issues disclosed herein. Certain embodiments may provide oneor more of the following technical advantage(s). For instance, certainembodiments enable a UE Context transfer from RAN nodes that share acommon RAN node addressing space. The proposed solutions do not requireon the identifiers coordination between RAN Sharing operators.Furthermore, the proposed solutions avoid ambiguities on the UEidentifier (Resume ID) which could have a negative impact on the UEperformance e.g. battery consumption, delays, due to unnecessarysignalling. Certain embodiments may provide some, none, or all of theseadvantages. Other technical advantages may be readily apparent to one ofskill in the art.

More particularly, the solutions disclosed in this document introducethe concept of the PLMN-specific RAN node identity that is associatedwith the UE's Resume ID (e.g. it could be included in the Resume ID ormapped to the Resume ID using a data base or lookup table). This hasfurther consequences on the UE RAN paging procedure that includes theResume ID as UE's identity in the paging message sent over the radiointerface.

Given that the RAN node identity included in the Resume ID is using acommon addressing space shared by the operators involved in the RANSharing scenario, it is ambiguous when presented in the paging messageto UEs registered to the different PLMNs (operators), i.e. multiple UEsregistered with different PLMNs (operators) would potentially reply tothat paging message as they may have the same RAN node identity in theirResume IDs.

According to some embodiments, a solution to the problem is theinclusion of an index value (or other information) referring to the UE'sregistered PLMN. In case it is an index value the index may point at aPLMN on the PLMN list broadcasted in the system information in the cellwhere the UE is paged. In order for the paging node to know which PLMNto indicate it needs to receive this information from the nodeinitiating the paging, which could be the RAN node storing the UEcontext. This information could be provided over X2 or Xn or S1 or NG-Csignaling between RAN nodes, and between CN and RAN nodes. Theinformation can be transferred as part of the paging message.

In scenarios where different cells paging the UE may broadcast the pagedUE's registered PLMN identity at different positions, the RAN nodeinitiating the paging process and compiling the Paging message thatmight be sent to other RAN nodes, either via the inter RAN node Xninterface or via the 5G CN via the N2/NG-C interface (see FIG. 14),shall include the paged UE's registered PLMN identity as part of themessage that will be consumed by the RAN node that sends the paging overthe radio interface.

The RAN node that sends the paging over the radio interface inserts theindex referring to the UE's registered PLMN as it is broadcast in thesystem information (i.e. position among the PLMNs being broadcast).

In a specific embodiment of the present disclosure, and to combatchallenges with coordination needs in, e.g., Multi-Operator CoreNetworks (MOCN) a cell identity and a tracking area code may beintroduced to be valid per PLMN. With this may also follow that a RANArea is separate per PLMN, for example if a RAN Area is associated witha set of cell ID's (where the Cell ID's are PLMN)

For Shared RAN, e.g., like MOCN, or other types of shared deployments,in particular Neutral Host operator deployments, another identifier tohandle is the resume ID that is used both for RAN paging of the UE, RANArea updates and when a UE trigger a transition from RRC_INACTIVE toRRC_CONNECTED, for purposes of transmitting UL data.

In E-UTRAN/LTE the resume ID is constructed including a combination ofthe eNB ID (20 bits) and a eNB specific UE identity (20 bits). It iscurrently not decided exactly how the Resume ID will be constructed inNR, but from a UE perspective though, the resume ID should only be arandom number, irrespective of how it is constructed.

When the Resume ID is received, e.g., in RRCConnectionResumeRequest andif the context is not stored in the receiving gNB, the context needs tobe fetched from another node. If the receiving gNB is a gNB servingmultiple PLMN's, there is currently no obvious way of knowing what othergNB's that may hold the context of the UE and with many PLMN's, it couldquickly become many other gNB's to inquire about context informationfrom, in several PLMN's. Thus, receiving a resume ID in a gNB servingseveral PLMN's, if context is not stored in the same gNB, it may benecessary to attempt to fetch the context from one of many differentgNB's, belonging to different PLMN's. One way of addressing this is tosomehow divide or coordinate the usage of the resume ID's, such that agNB receiving a resume ID will immediately be able to connect it to aspecific PLMN and then implicitly be able to limit the amount of othernodes to inquire about context ID. It would be attractive if thiscoordination could be avoided as it will affect the amount of resumeID's in all PLMN's that share a RAN node. To address the minimization ofcoordination between different PLMN's, according to a specificembodiment of the present invention, the Resume ID is made valid onlyper Registered PLMN and this Registered PLMN would then need to beincluded in UE-initiated signaling, e.g.,RRCConnectionResumeRequest/msg3 and stored with/in the UE context.

Including the PLMN identity would remove any need for coordination overPLMN borders, it would be more feasible to handle resume requests ingNB's serving several PLMN's and each PLMN would have the complete setof Resume ID's available to use. Thus, the registered PLMN should beincluded in initial signaling together with a Resume ID, or otherindication that points to a UE Context in the RAN. Similarly, theRegistered PLMN may also be stored in the UE Context in the network(e.g., RAN) in connection to initial creation of the context.

According to other aspects of the present disclosure, a PLMN indicationis also included in RAN Area Paging.

There are different ways to include a PLMN ID. Including the completePLMN ID will be bit costly and even though it is possible, it may bepreferable to indicate the PLMN with an index, for example given fromsystem information where an index for each supported PLMN may be set.

In some embodiments of the present disclosure, the Resume ID may beassociated with a specific PLMN ID which may be indicated to the UE withdedicated signaling when the network provides the UE with the Resume IDor with common signaling, e.g., in system information. The specific PLMNID may be indicated explicitly or as an index which may point at a PLMNon the PLMN list broadcasted in the system information. The specificPLMN ID may be the registered PLMN of the UE. That the PLMN IDassociated with the Resume ID is the registered PLMN of the UE may beindicated explicitly (e.g., with a special indicator) or with aspecial/predefined index code point. The specific PLMN ID may be theprimary PLMN pertaining to a cell or PSS/SSS. That the PLMN IDassociated with the Resume ID is the primary PLMN of a cell or PSS/SSSmay be indicated explicitly or with a special index code point.

As described above, when the UE requests a transition from RRC_INACTIVEstate to RRC_CONNECTED state, the UE indicates to the network thespecific PLMN ID which the Resume ID is associated with and the ResumeID. The indication of the specific PLMN ID may be the explicit/full PLMNID, or an index value indicating a specific PLMN on a PLMN list that thecell which the UE is connecting to has provided to the UE (E.g. viabroadcast channel). Other codings are also possible. When the Resume IDis associated with the primary PLMN of the cell or PSS/SSS where it wasassigned and the primary PLMN of the cell or PSS/SSS where thetransition from RRC_INACTIVE to RRC_CONNECTED is requested, theindication may be a special/predefined index code point, a specialindicator or absence of indication of associated PLMN ID.

In some embodiments of the present disclosure, the UE attempts/requeststransition from RRC_INACTIVE state to RRC_CONNECTED state only when thePLMN with which the Resume ID is associated is available.

In some embodiments of the present disclosure, the UE attempts/requeststransition from RRC_INACTIVE state to RRC_CONNECTED state only when theUE's registered PLMN is available.

In some embodiments of the present disclosure, when the PLMN with whichthe Resume ID is associated is not available, the UE does notattempt/request transition from RRC_INACTIVE state to RRC_CONNECTEDstate, but leaves RRC_INACTIVE state (or goes to RRC_IDLE state), andattempts/requests establishment of a new connection.

In some embodiments of the present disclosure, when the UE's registeredPLMN is not available, the UE does not attempt/request transition fromRRC_INACTIVE state to RRC_CONNECTED state, but leaves RRC_INACTIVE state(or goes to RRC_IDLE state), and attempts/requests establishment of anew connection.

Although the subject matter described herein may be implemented in anyappropriate type of system using any suitable components, theembodiments disclosed herein are described in relation to a wirelessnetwork, such as the example wireless network illustrated in FIG. 15.For simplicity, the wireless network of FIG. 15 only depicts network1506, network nodes 1560 and 1560 b, and WDs 1510, 1510 b, and 1510 c.In practice, a wireless network may further include any additionalelements suitable to support communication between wireless devices orbetween a wireless device and another communication device, such as alandline telephone, a service provider, or any other network node or enddevice. Of the illustrated components, network node 1560 and wirelessdevice (WD) 1510 are depicted with additional detail. The wirelessnetwork may provide communication and other types of services to one ormore wireless devices to facilitate the wireless devices' access toand/or use of the services provided by, or via, the wireless network.

The wireless network may comprise and/or interface with any type ofcommunication, telecommunication, data, cellular, and/or radio networkor other similar type of system. In some embodiments, the wirelessnetwork may be configured to operate according to specific standards orother types of predefined rules or procedures. Thus, particularembodiments of the wireless network may implement communicationstandards, such as Global System for Mobile Communications (GSM),Universal Mobile Telecommunications System (UMTS), Long Term Evolution(LTE), and/or other suitable 2G, 3G, 4G, or 5G standards; wireless localarea network (WLAN) standards, such as the IEEE 802.11 standards; and/orany other appropriate wireless communication standard, such as theWorldwide Interoperability for Microwave Access (WiMax), Bluetooth,Z-Wave and/or ZigBee standards.

Network 1506 may comprise one or more backhaul networks, core networks,IP networks, public switched telephone networks (PSTNs), packet datanetworks, optical networks, wide-area networks (WANs), local areanetworks (LANs), wireless local area networks (WLANs), wired networks,wireless networks, metropolitan area networks, and other networks toenable communication between devices.

Network node 1560 and WD 1510 comprise various components described inmore detail below. These components work together in order to providenetwork node and/or wireless device functionality, such as providingwireless connections in a wireless network. In different embodiments,the wireless network may comprise any number of wired or wirelessnetworks, network nodes, base stations, controllers, wireless devices,relay stations, and/or any other components or systems that mayfacilitate or participate in the communication of data and/or signalswhether via wired or wireless connections.

As used herein, network node refers to equipment capable, configured,arranged and/or operable to communicate directly or indirectly with awireless device and/or with other network nodes or equipment in thewireless network to enable and/or provide wireless access to thewireless device and/or to perform other functions (e.g., administration)in the wireless network. Examples of network nodes include, but are notlimited to, access points (APs) (e.g., radio access points), basestations (BSs) (e.g., radio base stations, Node Bs, and evolved Node Bs(eNBs)). Base stations may be categorized based on the amount ofcoverage they provide (or, stated differently, their transmit powerlevel) and may then also be referred to as femto base stations, picobase stations, micro base stations, or macro base stations. A basestation may be a relay node or a relay donor node controlling a relay. Anetwork node may also include one or more (or all) parts of adistributed radio base station such as centralized digital units and/orremote radio units (RRUs), sometimes referred to as Remote Radio Heads(RRHs). Such remote radio units may or may not be integrated with anantenna as an antenna integrated radio. Parts of a distributed radiobase station may also be referred to as nodes in a distributed antennasystem (DAS). Yet further examples of network nodes includemulti-standard radio (MSR) equipment such as MSR BSs, networkcontrollers such as radio network controllers (RNCs) or base stationcontrollers (BSCs), base transceiver stations (BTSs), transmissionpoints, transmission nodes, multi-cell/multicast coordination entities(MCEs), core network nodes (e.g., MSCs, MMEs), O&M nodes, OSS nodes, SONnodes, positioning nodes (e.g., E-SMLCs), and/or MDTs. As anotherexample, a network node may be a virtual network node as described inmore detail below. More generally, however, network nodes may representany suitable device (or group of devices) capable, configured, arranged,and/or operable to enable and/or provide a wireless device with accessto the wireless network or to provide some service to a wireless devicethat has accessed the wireless network.

In FIG. 15, network node 1560 includes processing circuitry 1570, devicereadable medium 1580, interface 1590, auxiliary equipment 1584, powersource 1586, power circuitry 1587, and antenna 1562. Although networknode 1560 illustrated in the example wireless network of FIG. 1 mayrepresent a device that includes the illustrated combination of hardwarecomponents, other embodiments may comprise network nodes with differentcombinations of components. It is to be understood that a network nodecomprises any suitable combination of hardware and/or software needed toperform the tasks, features, functions and methods disclosed herein.Moreover, while the components of network node 1560 are depicted assingle boxes located within a larger box, or nested within multipleboxes, in practice, a network node may comprise multiple differentphysical components that make up a single illustrated component (e.g.,device readable medium 1580 may comprise multiple separate hard drivesas well as multiple RAM modules).

Similarly, network node 1560 may be composed of multiple physicallyseparate components (e.g., a NodeB component and a RNC component, or aBTS component and a BSC component, etc.), which may each have their ownrespective components. In certain scenarios in which network node 1560comprises multiple separate components (e.g., BTS and BSC components),one or more of the separate components may be shared among severalnetwork nodes. For example, a single RNC may control multiple NodeB's.In such a scenario, each unique NodeB and RNC pair, may in someinstances be considered a single separate network node. In someembodiments, network node 1560 may be configured to support multipleradio access technologies (RATs). In such embodiments, some componentsmay be duplicated (e.g., separate device readable medium 1580 for thedifferent RATs) and some components may be reused (e.g., the sameantenna 1562 may be shared by the RATs). Network node 1560 may alsoinclude multiple sets of the various illustrated components fordifferent wireless technologies integrated into network node 1560, suchas, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wirelesstechnologies. These wireless technologies may be integrated into thesame or different chip or set of chips and other components withinnetwork node 1560.

Processing circuitry 1570 is configured to perform any determining,calculating, or similar operations (e.g., certain obtaining operations)described herein as being provided by a network node. These operationsperformed by processing circuitry 1570 may include processinginformation obtained by processing circuitry 1570 by, for example,converting the obtained information into other information, comparingthe obtained information or converted information to information storedin the network node, and/or performing one or more operations based onthe obtained information or converted information, and as a result ofsaid processing making a determination.

Processing circuitry 1570 may comprise a combination of one or more of amicroprocessor, controller, microcontroller, central processing unit,digital signal processor, application-specific integrated circuit, fieldprogrammable gate array, or any other suitable computing device,resource, or combination of hardware, software and/or encoded logicoperable to provide, either alone or in conjunction with other networknode 1560 components, such as device readable medium 1580, network node1560 functionality. For example, processing circuitry 1570 may executeinstructions stored in device readable medium 1580 or in memory withinprocessing circuitry 1570. Such functionality may include providing anyof the various wireless features, functions, or benefits discussedherein. In some embodiments, processing circuitry 1570 may include asystem on a chip (SOC).

In some embodiments, processing circuitry 1570 may include one or moreof radio frequency (RF) transceiver circuitry 1572 and basebandprocessing circuitry 1574. In some embodiments, radio frequency (RF)transceiver circuitry 1572 and baseband processing circuitry 1574 may beon separate chips (or sets of chips), boards, or units, such as radiounits and digital units. In alternative embodiments, part or all of RFtransceiver circuitry 1572 and baseband processing circuitry 1574 may beon the same chip or set of chips, boards, or units

In certain embodiments, some or all of the functionality describedherein as being provided by a network node, base station, eNB or othersuch network device may be performed by processing circuitry 1570executing instructions stored on device readable medium 1580 or memorywithin processing circuitry 1570. In alternative embodiments, some orall of the functionality may be provided by processing circuitry 1570without executing instructions stored on a separate or discrete devicereadable medium, such as in a hard-wired manner. In any of thoseembodiments, whether executing instructions stored on a device readablestorage medium or not, processing circuitry 1570 can be configured toperform the described functionality. The benefits provided by suchfunctionality are not limited to processing circuitry 1570 alone or toother components of network node 1560, but are enjoyed by network node1560 as a whole, and/or by end users and the wireless network generally.

Device readable medium 1580 may comprise any form of volatile ornon-volatile computer readable memory including, without limitation,persistent storage, solid-state memory, remotely mounted memory,magnetic media, optical media, random access memory (RAM), read-onlymemory (ROM), mass storage media (for example, a hard disk), removablestorage media (for example, a flash drive, a Compact Disk (CD) or aDigital Video Disk (DVD)), and/or any other volatile or non-volatile,non-transitory device readable and/or computer-executable memory devicesthat store information, data, and/or instructions that may be used byprocessing circuitry 1570. Device readable medium 1580 may store anysuitable instructions, data or information, including a computerprogram, software, an application including one or more of logic, rules,code, tables, etc. and/or other instructions capable of being executedby processing circuitry 1570 and, utilized by network node 1560. Devicereadable medium 1580 may be used to store any calculations made byprocessing circuitry 1570 and/or any data received via interface 1590.In some embodiments, processing circuitry 1570 and device readablemedium 1580 may be considered to be integrated.

Interface 1590 is used in the wired or wireless communication ofsignalling and/or data between network node 1560, network 1506, and/orWDs 1510. As illustrated, interface 1590 comprises port(s)/terminal(s)1594 to send and receive data, for example to and from network 1506 overa wired connection. Interface 1590 also includes radio front endcircuitry 1592 that may be coupled to, or in certain embodiments a partof, antenna 1562. Radio front end circuitry 1592 comprises filters 1598and amplifiers 1596. Radio front end circuitry 1592 may be connected toantenna 1562 and processing circuitry 1570. Radio front end circuitrymay be configured to condition signals communicated between antenna 1562and processing circuitry 1570. Radio front end circuitry 1592 mayreceive digital data that is to be sent out to other network nodes orWDs via a wireless connection. Radio front end circuitry 1592 mayconvert the digital data into a radio signal having the appropriatechannel and bandwidth parameters using a combination of filters 1598and/or amplifiers 1596. The radio signal may then be transmitted viaantenna 1562. Similarly, when receiving data, antenna 1562 may collectradio signals which are then converted into digital data by radio frontend circuitry 1592. The digital data may be passed to processingcircuitry 1570. In other embodiments, the interface may comprisedifferent components and/or different combinations of components.

In certain alternative embodiments, network node 1560 may not includeseparate radio front end circuitry 1592, instead, processing circuitry1570 may comprise radio front end circuitry and may be connected toantenna 1562 without separate radio front end circuitry 1592. Similarly,in some embodiments, all or some of RF transceiver circuitry 1572 may beconsidered a part of interface 1590. In still other embodiments,interface 1590 may include one or more ports or terminals 1594, radiofront end circuitry 1592, and RF transceiver circuitry 1572, as part ofa radio unit (not shown), and interface 1590 may communicate withbaseband processing circuitry 1574, which is part of a digital unit (notshown).

Antenna 1562 may include one or more antennas, or antenna arrays,configured to send and/or receive wireless signals. Antenna 1562 may becoupled to radio front end circuitry 1590 and may be any type of antennacapable of transmitting and receiving data and/or signals wirelessly. Insome embodiments, antenna 1562 may comprise one or moreomni-directional, sector or panel antennas operable to transmit/receiveradio signals between, for example, 2 GHz and 66 GHz. Anomni-directional antenna may be used to transmit/receive radio signalsin any direction, a sector antenna may be used to transmit/receive radiosignals from devices within a particular area, and a panel antenna maybe a line of sight antenna used to transmit/receive radio signals in arelatively straight line. In some instances, the use of more than oneantenna may be referred to as MIMO. In certain embodiments, antenna 1562may be separate from network node 1560 and may be connectable to networknode 1560 through an interface or port.

Antenna 1562, interface 1590, and/or processing circuitry 1570 may beconfigured to perform any receiving operations and/or certain obtainingoperations described herein as being performed by a network node. Anyinformation, data and/or signals may be received from a wireless device,another network node and/or any other network equipment. Similarly,antenna 1562, interface 1590, and/or processing circuitry 1570 may beconfigured to perform any transmitting operations described herein asbeing performed by a network node. Any information, data and/or signalsmay be transmitted to a wireless device, another network node and/or anyother network equipment.

Power circuitry 1587 may comprise, or be coupled to, power managementcircuitry and is configured to supply the components of network node1560 with power for performing the functionality described herein. Powercircuitry 1587 may receive power from power source 1586. Power source1586 and/or power circuitry 1587 may be configured to provide power tothe various components of network node 1560 in a form suitable for therespective components (e.g., at a voltage and current level needed foreach respective component). Power source 1586 may either be included in,or external to, power circuitry 1587 and/or network node 1560. Forexample, network node 1560 may be connectable to an external powersource (e.g., an electricity outlet) via an input circuitry or interfacesuch as an electrical cable, whereby the external power source suppliespower to power circuitry 1587. As a further example, power source 1586may comprise a source of power in the form of a battery or battery packwhich is connected to, or integrated in, power circuitry 1587. Thebattery may provide backup power should the external power source fail.Other types of power sources, such as photovoltaic devices, may also beused.

Alternative embodiments of network node 1560 may include additionalcomponents beyond those shown in FIG. 15 that may be responsible forproviding certain aspects of the network node's functionality, includingany of the functionality described herein and/or any functionalitynecessary to support the subject matter described herein. For example,network node 1560 may include user interface equipment to allow input ofinformation into network node 1560 and to allow output of informationfrom network node 1560. This may allow a user to perform diagnostic,maintenance, repair, and other administrative functions for network node1560.

As used herein, wireless device (WD) refers to a device capable,configured, arranged and/or operable to communicate wirelessly withnetwork nodes and/or other wireless devices. Unless otherwise noted, theterm WD may be used interchangeably herein with user equipment (UE).Communicating wirelessly may involve transmitting and/or receivingwireless signals using electromagnetic waves, radio waves, infraredwaves, and/or other types of signals suitable for conveying informationthrough air. In some embodiments, a WD may be configured to transmitand/or receive information without direct human interaction. Forinstance, a WD may be designed to transmit information to a network on apredetermined schedule, when triggered by an internal or external event,or in response to requests from the network. Examples of a WD include,but are not limited to, a smart phone, a mobile phone, a cell phone, avoice over IP (VoIP) phone, a wireless local loop phone, a desktopcomputer, a personal digital assistant (PDA), a wireless cameras, agaming console or device, a music storage device, a playback appliance,a wearable terminal device, a wireless endpoint, a mobile station, atablet, a laptop, a laptop-embedded equipment (LEE), a laptop-mountedequipment (LME), a smart device, a wireless customer-premise equipment(CPE). a vehicle-mounted wireless terminal device, etc. A WD may supportdevice-to-device (D2D) communication, for example by implementing a 3GPPstandard for sidelink communication, and may in this case be referred toas a D2D communication device. As yet another specific example, in anInternet of Things (IoT) scenario, a WD may represent a machine or otherdevice that performs monitoring and/or measurements, and transmits theresults of such monitoring and/or measurements to another WD and/or anetwork node. The WD may in this case be a machine-to-machine (M2M)device, which may in a 3GPP context be referred to as a machine-typecommunication (MTC) device. As one particular example, the WD may be aUE implementing the 3GPP narrow band internet of things (NB-IoT)standard. Particular examples of such machines or devices are sensors,metering devices such as power meters, industrial machinery, or home orpersonal appliances (e.g. refrigerators, televisions, etc.) personalwearables (e.g., watches, fitness trackers, etc.). In other scenarios, aWD may represent a vehicle or other equipment that is capable ofmonitoring and/or reporting on its operational status or other functionsassociated with its operation. A WD as described above may represent theendpoint of a wireless connection, in which case the device may bereferred to as a wireless terminal. Furthermore, a WD as described abovemay be mobile, in which case it may also be referred to as a mobiledevice or a mobile terminal.

As illustrated, wireless device 1510 includes antenna 1511, interface1514, processing circuitry 1520, device readable medium 1530, userinterface equipment 1532, auxiliary equipment 1534, power source 1536and power circuitry 1537. WD 1510 may include multiple sets of one ormore of the illustrated components for different wireless technologiessupported by WD 1510, such as, for example, GSM, WCDMA, LTE, NR, WiFi,WiMAX, or Bluetooth wireless technologies, just to mention a few. Thesewireless technologies may be integrated into the same or different chipsor set of chips as other components within WD 1510.

Antenna 1511 may include one or more antennas or antenna arrays,configured to send and/or receive wireless signals, and is connected tointerface 1514. In certain alternative embodiments, antenna 1511 may beseparate from WD 1510 and be connectable to WD 1510 through an interfaceor port. Antenna 1511, interface 1514, and/or processing circuitry 1520may be configured to perform any receiving or transmitting operationsdescribed herein as being performed by a WD. Any information, dataand/or signals may be received from a network node and/or another WD. Insome embodiments, radio front end circuitry and/or antenna 1511 may beconsidered an interface.

As illustrated, interface 1514 comprises radio front end circuitry 1512and antenna 1511. Radio front end circuitry 1512 comprise one or morefilters 1518 and amplifiers 1516. Radio front end circuitry 1514 isconnected to antenna 1511 and processing circuitry 1520, and isconfigured to condition signals communicated between antenna 1511 andprocessing circuitry 1520. Radio front end circuitry 1512 may be coupledto or a part of antenna 1511. In some embodiments, WD 1510 may notinclude separate radio front end circuitry 1512; rather, processingcircuitry 1520 may comprise radio front end circuitry and may beconnected to antenna 1511. Similarly, in some embodiments, some or allof RF transceiver circuitry 1522 may be considered a part of interface1514. Radio front end circuitry 1512 may receive digital data that is tobe sent out to other network nodes or WDs via a wireless connection.Radio front end circuitry 1512 may convert the digital data into a radiosignal having the appropriate channel and bandwidth parameters using acombination of filters 1518 and/or amplifiers 1516. The radio signal maythen be transmitted via antenna 1511. Similarly, when receiving data,antenna 1511 may collect radio signals which are then converted intodigital data by radio front end circuitry 1512. The digital data may bepassed to processing circuitry 1520. In other embodiments, the interfacemay comprise different components and/or different combinations ofcomponents.

Processing circuitry 1520 may comprise a combination of one or more of amicroprocessor, controller, microcontroller, central processing unit,digital signal processor, application-specific integrated circuit, fieldprogrammable gate array, or any other suitable computing device,resource, or combination of hardware, software, and/or encoded logicoperable to provide, either alone or in conjunction with other WD 1510components, such as device readable medium 1530, WD 1510 functionality.Such functionality may include providing any of the various wirelessfeatures or benefits discussed herein. For example, processing circuitry1520 may execute instructions stored in device readable medium 1530 orin memory within processing circuitry 1520 to provide the functionalitydisclosed herein.

As illustrated, processing circuitry 1520 includes one or more of RFtransceiver circuitry 1522, baseband processing circuitry 1524, andapplication processing circuitry 1526. In other embodiments, theprocessing circuitry may comprise different components and/or differentcombinations of components. In certain embodiments processing circuitry1520 of WD 1510 may comprise a SOC. In some embodiments, RF transceivercircuitry 1522, baseband processing circuitry 1524, and applicationprocessing circuitry 1526 may be on separate chips or sets of chips. Inalternative embodiments, part or all of baseband processing circuitry1524 and application processing circuitry 1526 may be combined into onechip or set of chips, and RF transceiver circuitry 1522 may be on aseparate chip or set of chips. In still alternative embodiments, part orall of RF transceiver circuitry 1522 and baseband processing circuitry1524 may be on the same chip or set of chips, and application processingcircuitry 1526 may be on a separate chip or set of chips. In yet otheralternative embodiments, part or all of RF transceiver circuitry 1522,baseband processing circuitry 1524, and application processing circuitry1526 may be combined in the same chip or set of chips. In someembodiments, RF transceiver circuitry 1522 may be a part of interface1514. RF transceiver circuitry 1522 may condition RF signals forprocessing circuitry 1520.

In certain embodiments, some or all of the functionality describedherein as being performed by a WD may be provided by processingcircuitry 1520 executing instructions stored on device readable medium1530, which in certain embodiments may be a computer-readable storagemedium. In alternative embodiments, some or all of the functionality maybe provided by processing circuitry 1520 without executing instructionsstored on a separate or discrete device readable storage medium, such asin a hard-wired manner. In any of those particular embodiments, whetherexecuting instructions stored on a device readable storage medium ornot, processing circuitry 1520 can be configured to perform thedescribed functionality. The benefits provided by such functionality arenot limited to processing circuitry 1520 alone or to other components ofWD 1510, but are enjoyed by WD 1510 as a whole, and/or by end users andthe wireless network generally.

Processing circuitry 1520 may be configured to perform any determining,calculating, or similar operations (e.g., certain obtaining operations)described herein as being performed by a WD. These operations, asperformed by processing circuitry 1520, may include processinginformation obtained by processing circuitry 1520 by, for example,converting the obtained information into other information, comparingthe obtained information or converted information to information storedby WD 1510, and/or performing one or more operations based on theobtained information or converted information, and as a result of saidprocessing making a determination.

Device readable medium 1530 may be operable to store a computer program,software, an application including one or more of logic, rules, code,tables, etc. and/or other instructions capable of being executed byprocessing circuitry 1520. Device readable medium 1530 may includecomputer memory (e.g., Random Access Memory (RAM) or Read Only Memory(ROM)), mass storage media (e.g., a hard disk), removable storage media(e.g., a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or anyother volatile or non-volatile, non-transitory device readable and/orcomputer executable memory devices that store information, data, and/orinstructions that may be used by processing circuitry 1520. In someembodiments, processing circuitry 1520 and device readable medium 1530may be considered to be integrated.

User interface equipment 1532 may provide components that allow for ahuman user to interact with WD 1510. Such interaction may be of manyforms, such as visual, audial, tactile, etc. User interface equipment1532 may be operable to produce output to the user and to allow the userto provide input to WD 1510. The type of interaction may vary dependingon the type of user interface equipment 1532 installed in WD 1510. Forexample, if WD 1510 is a smart phone, the interaction may be via a touchscreen; if WD 1510 is a smart meter, the interaction may be through ascreen that provides usage (e.g., the number of gallons used) or aspeaker that provides an audible alert (e.g., if smoke is detected).User interface equipment 1532 may include input interfaces, devices andcircuits, and output interfaces, devices and circuits. User interfaceequipment 1532 is configured to allow input of information into WD 1510,and is connected to processing circuitry 1520 to allow processingcircuitry 1520 to process the input information. User interfaceequipment 1532 may include, for example, a microphone, a proximity orother sensor, keys/buttons, a touch display, one or more cameras, a USBport, or other input circuitry. User interface equipment 1532 is alsoconfigured to allow output of information from WD 1510, and to allowprocessing circuitry 1520 to output information from WD 1510. Userinterface equipment 1532 may include, for example, a speaker, a display,vibrating circuitry, a USB port, a headphone interface, or other outputcircuitry. Using one or more input and output interfaces, devices, andcircuits, of user interface equipment 1532, WD 1510 may communicate withend users and/or the wireless network, and allow them to benefit fromthe functionality described herein.

Auxiliary equipment 1534 is operable to provide more specificfunctionality which may not be generally performed by WDs. This maycomprise specialized sensors for doing measurements for variouspurposes, interfaces for additional types of communication such as wiredcommunications etc. The inclusion and type of components of auxiliaryequipment 1534 may vary depending on the embodiment and/or scenario.

Power source 1536 may, in some embodiments, be in the form of a batteryor battery pack. Other types of power sources, such as an external powersource (e.g., an electricity outlet), photovoltaic devices or powercells, may also be used. WD 1510 may further comprise power circuitry1537 for delivering power from power source 1536 to the various parts ofWD 1510 which need power from power source 1536 to carry out anyfunctionality described or indicated herein. Power circuitry 1537 may incertain embodiments comprise power management circuitry. Power circuitry1537 may additionally or alternatively be operable to receive power froman external power source; in which case WD 1510 may be connectable tothe external power source (such as an electricity outlet) via inputcircuitry or an interface such as an electrical power cable. Powercircuitry 1537 may also in certain embodiments be operable to deliverpower from an external power source to power source 1536. This may be,for example, for the charging of power source 1536. Power circuitry 1537may perform any formatting, converting, or other modification to thepower from power source 1536 to make the power suitable for therespective components of WD 1510 to which power is supplied.

FIG. 16 illustrates one embodiment of a UE in accordance with variousaspects described herein. As used herein, a user equipment or UE may notnecessarily have a user in the sense of a human user who owns and/oroperates the relevant device. Instead, a UE may represent a device thatis intended for sale to, or operation by, a human user but which maynot, or which may not initially, be associated with a specific humanuser. A UE may also comprise any UE identified by the 3^(rd) GenerationPartnership Project (3GPP), including a NB-IoT UE that is not intendedfor sale to, or operation by, a human user. UE 1600, as illustrated inFIG. 16, is one example of a WD configured for communication inaccordance with one or more communication standards promulgated by the3^(rd) Generation Partnership Project (3GPP), such as 3GPP's GSM, UMTS,LTE, and/or 5G standards. As mentioned previously, the term WD and UEmay be used interchangeable. Accordingly, although FIG. 16 is a UE, thecomponents discussed herein are equally applicable to a WD, andvice-versa.

In FIG. 16, UE 1600 includes processing circuitry 1601 that isoperatively coupled to input/output interface 1605, radio frequency (RF)interface 1609, network connection interface 1611, memory 1615 includingrandom access memory (RAM) 1617, read-only memory (ROM) 1619, andstorage medium 1621 or the like, communication subsystem 1631, powersource 1633, and/or any other component, or any combination thereof.Storage medium 1621 includes operating system 1623, application program1625, and data 1627. In other embodiments, storage medium 1621 mayinclude other similar types of information. Certain UEs may utilize allof the components shown in FIG. 16, or only a subset of the components.The level of integration between the components may vary from one UE toanother UE. Further, certain UEs may contain multiple instances of acomponent, such as multiple processors, memories, transceivers,transmitters, receivers, etc.

In FIG. 16, processing circuitry 1601 may be configured to processcomputer instructions and data. Processing circuitry 1601 may beconfigured to implement any sequential state machine operative toexecute machine instructions stored as machine-readable computerprograms in the memory, such as one or more hardware-implemented statemachines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logictogether with appropriate firmware; one or more stored program,general-purpose processors, such as a microprocessor or Digital SignalProcessor (DSP), together with appropriate software; or any combinationof the above. For example, the processing circuitry 1601 may include twocentral processing units (CPUs). Data may be information in a formsuitable for use by a computer.

In the depicted embodiment, input/output interface 1605 may beconfigured to provide a communication interface to an input device,output device, or input and output device. UE 1600 may be configured touse an output device via input/output interface 1605. An output devicemay use the same type of interface port as an input device. For example,a USB port may be used to provide input to and output from UE 1600. Theoutput device may be a speaker, a sound card, a video card, a display, amonitor, a printer, an actuator, an emitter, a smartcard, another outputdevice, or any combination thereof. UE 1600 may be configured to use aninput device via input/output interface 1605 to allow a user to captureinformation into UE 1600. The input device may include a touch-sensitiveor presence-sensitive display, a camera (e.g., a digital camera, adigital video camera, a web camera, etc.), a microphone, a sensor, amouse, a trackball, a directional pad, a trackpad, a scroll wheel, asmartcard, and the like. The presence-sensitive display may include acapacitive or resistive touch sensor to sense input from a user. Asensor may be, for instance, an accelerometer, a gyroscope, a tiltsensor, a force sensor, a magnetometer, an optical sensor, a proximitysensor, another like sensor, or any combination thereof. For example,the input device may be an accelerometer, a magnetometer, a digitalcamera, a microphone, and an optical sensor.

In FIG. 16, RF interface 1609 may be configured to provide acommunication interface to RF components such as a transmitter, areceiver, and an antenna. Network connection interface 1611 may beconfigured to provide a communication interface to network 1643 a.Network 1643 a may encompass wired and/or wireless networks such as alocal-area network (LAN), a wide-area network (WAN), a computer network,a wireless network, a telecommunications network, another like networkor any combination thereof. For example, network 1643 a may comprise aWi-Fi network. Network connection interface 1611 may be configured toinclude a receiver and a transmitter interface used to communicate withone or more other devices over a communication network according to oneor more communication protocols, such as Ethernet, TCP/IP, SONET, ATM,or the like. Network connection interface 1611 may implement receiverand transmitter functionality appropriate to the communication networklinks (e.g., optical, electrical, and the like). The transmitter andreceiver functions may share circuit components, software or firmware,or alternatively may be implemented separately.

RAM 1617 may be configured to interface via bus 1602 to processingcircuitry 1601 to provide storage or caching of data or computerinstructions during the execution of software programs such as theoperating system, application programs, and device drivers. ROM 1619 maybe configured to provide computer instructions or data to processingcircuitry 1601. For example, ROM 1619 may be configured to storeinvariant low-level system code or data for basic system functions suchas basic input and output (I/O), startup, or reception of keystrokesfrom a keyboard that are stored in a non-volatile memory. Storage medium1621 may be configured to include memory such as RAM, ROM, programmableread-only memory (PROM), erasable programmable read-only memory (EPROM),electrically erasable programmable read-only memory (EEPROM), magneticdisks, optical disks, floppy disks, hard disks, removable cartridges, orflash drives. In one example, storage medium 1621 may be configured toinclude operating system 1623, application program 1625 such as a webbrowser application, a widget or gadget engine or another application,and data file 1627. Storage medium 1621 may store, for use by UE 1600,any of a variety of various operating systems or combinations ofoperating systems.

Storage medium 1621 may be configured to include a number of physicaldrive units, such as redundant array of independent disks (RAID), floppydisk drive, flash memory, USB flash drive, external hard disk drive,thumb drive, pen drive, key drive, high-density digital versatile disc(HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray opticaldisc drive, holographic digital data storage (HDDS) optical disc drive,external mini-dual in-line memory module (DIMM), synchronous dynamicrandom access memory (SDRAM), external micro-DIMM SDRAM, smartcardmemory such as a subscriber identity module or a removable user identity(SIM/RUIM) module, other memory, or any combination thereof. Storagemedium 1621 may allow UE 1600 to access computer-executableinstructions, application programs or the like, stored on transitory ornon-transitory memory media, to off-load data, or to upload data. Anarticle of manufacture, such as one utilizing a communication system maybe tangibly embodied in storage medium 1621, which may comprise a devicereadable medium.

In FIG. 16, processing circuitry 1601 may be configured to communicatewith network 1643 b using communication subsystem 1631. Network 1643 aand network 1643 b may be the same network or networks or differentnetwork or networks. Communication subsystem 1631 may be configured toinclude one or more transceivers used to communicate with network 1643b. For example, communication subsystem 1631 may be configured toinclude one or more transceivers used to communicate with one or moreremote transceivers of another device capable of wireless communicationsuch as another WD, UE, or base station of a radio access network (RAN)according to one or more communication protocols, such as IEEE 802.16,CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like. Each transceiver mayinclude transmitter 1633 and/or receiver 1635 to implement transmitteror receiver functionality, respectively, appropriate to the RAN links(e.g., frequency allocations and the like). Further, transmitter 1633and receiver 1635 of each transceiver may share circuit components,software or firmware, or alternatively may be implemented separately.

In the illustrated embodiment, the communication functions ofcommunication subsystem 1631 may include data communication, voicecommunication, multimedia communication, short-range communications suchas Bluetooth, near-field communication, location-based communicationsuch as the use of the global positioning system (GPS) to determine alocation, another like communication function, or any combinationthereof. For example, communication subsystem 1631 may include cellularcommunication, Wi-Fi communication, Bluetooth communication, and GPScommunication. Network 1643 b may encompass wired and/or wirelessnetworks such as a local-area network (LAN), a wide-area network (WAN),a computer network, a wireless network, a telecommunications network,another like network or any combination thereof. For example, network1643 b may be a cellular network, a Wi-Fi network, and/or a near-fieldnetwork. Power source 1613 may be configured to provide alternatingcurrent (AC) or direct current (DC) power to components of UE 1600.

The features, benefits and/or functions described herein may beimplemented in one of the components of UE 1600 or partitioned acrossmultiple components of UE 1600. Further, the features, benefits, and/orfunctions described herein may be implemented in any combination ofhardware, software or firmware. In one example, communication subsystem1631 may be configured to include any of the components describedherein. Further, processing circuitry 1601 may be configured tocommunicate with any of such components over bus 1602. In anotherexample, any of such components may be represented by programinstructions stored in memory that when executed by processing circuitry1601 perform the corresponding functions described herein. In anotherexample, the functionality of any of such components may be partitionedbetween processing circuitry 1601 and communication subsystem 1631. Inanother example, the non-computationally intensive functions of any ofsuch components may be implemented in software or firmware and thecomputationally intensive functions may be implemented in hardware.

FIG. 17 is a schematic block diagram illustrating a virtualizationenvironment 1700 in which functions implemented by some embodiments maybe virtualized. In the present context, virtualizing means creatingvirtual versions of apparatuses or devices which may includevirtualizing hardware platforms, storage devices and networkingresources. As used herein, virtualization can be applied to a node(e.g., a virtualized base station or a virtualized radio access node) orto a device (e.g., a UE, a wireless device or any other type ofcommunication device) or components thereof and relates to animplementation in which at least a portion of the functionality isimplemented as one or more virtual components (e.g., via one or moreapplications, components, functions, virtual machines or containersexecuting on one or more physical processing nodes in one or morenetworks).

In some embodiments, some or all of the functions described herein maybe implemented as virtual components executed by one or more virtualmachines implemented in one or more virtual environments 1700 hosted byone or more of hardware nodes 1730. Further, in embodiments in which thevirtual node is not a radio access node or does not require radioconnectivity (e.g., a core network node), then the network node may beentirely virtualized.

The functions may be implemented by one or more applications 1720 (whichmay alternatively be called software instances, virtual appliances,network functions, virtual nodes, virtual network functions, etc.)operative to implement some of the features, functions, and/or benefitsof some of the embodiments disclosed herein. Applications 1720 are runin virtualization environment 1700 which provides hardware 1730comprising processing circuitry 1760 and memory 1790. Memory 1790contains instructions 1795 executable by processing circuitry 1760whereby application 1720 is operative to provide one or more of thefeatures, benefits, and/or functions disclosed herein.

Virtualization environment 1700, comprises general-purpose orspecial-purpose network hardware devices 1730 comprising a set of one ormore processors or processing circuitry 1760, which may be commercialoff-the-shelf (COTS) processors, dedicated Application SpecificIntegrated Circuits (ASICs), or any other type of processing circuitryincluding digital or analog hardware components or special purposeprocessors. Each hardware device may comprise memory 1790-1 which may benon-persistent memory for temporarily storing instructions 1795 orsoftware executed by processing circuitry 1760. Each hardware device maycomprise one or more network interface controllers (NICs) 1770, alsoknown as network interface cards, which include physical networkinterface 1780. Each hardware device may also include non-transitory,persistent, machine-readable storage media 1790-2 having stored thereinsoftware 1795 and/or instructions executable by processing circuitry1760. Software 1795 may include any type of software including softwarefor instantiating one or more virtualization layers 1750 (also referredto as hypervisors), software to execute virtual machines 1740 as well assoftware allowing it to execute functions, features and/or benefitsdescribed in relation with some embodiments described herein.

Virtual machines 1740, comprise virtual processing, virtual memory,virtual networking or interface and virtual storage, and may be run by acorresponding virtualization layer 1750 or hypervisor. Differentembodiments of the instance of virtual appliance 1720 may be implementedon one or more of virtual machines 1740, and the implementations may bemade in different ways.

During operation, processing circuitry 1760 executes software 1795 toinstantiate the hypervisor or virtualization layer 1750, which maysometimes be referred to as a virtual machine monitor (VMM).Virtualization layer 1750 may present a virtual operating platform thatappears like networking hardware to virtual machine 1740.

As shown in FIG. 17, hardware 1730 may be a standalone network node withgeneric or specific components. Hardware 1730 may comprise antenna 17225and may implement some functions via virtualization. Alternatively,hardware 1730 may be part of a larger cluster of hardware (e.g. such asin a data center or customer premise equipment (CPE)) where manyhardware nodes work together and are managed via management andorchestration (MANO) 17100, which, among others, oversees lifecyclemanagement of applications 1720.

Virtualization of the hardware is in some contexts referred to asnetwork function virtualization (NFV). NFV may be used to consolidatemany network equipment types onto industry standard high volume serverhardware, physical switches, and physical storage, which can be locatedin data centers, and customer premise equipment.

In the context of NFV, virtual machine 1740 may be a softwareimplementation of a physical machine that runs programs as if they wereexecuting on a physical, non-virtualized machine. Each of virtualmachines 1740, and that part of hardware 1730 that executes that virtualmachine, be it hardware dedicated to that virtual machine and/orhardware shared by that virtual machine with others of the virtualmachines 1740, forms a separate virtual network elements (VNE).

Still in the context of NFV, Virtual Network Function (VNF) isresponsible for handling specific network functions that run in one ormore virtual machines 1740 on top of hardware networking infrastructure1730 and corresponds to application 1720 in FIG. 17.

In some embodiments, one or more radio units 17200 that each include oneor more transmitters 17220 and one or more receivers 17210 may becoupled to one or more antennas 17225. Radio units 17200 may communicatedirectly with hardware nodes 1730 via one or more appropriate networkinterfaces and may be used in combination with the virtual components toprovide a virtual node with radio capabilities, such as a radio accessnode or a base station.

In some embodiments, some signalling can be effected with the use ofcontrol system 17230 which may alternatively be used for communicationbetween the hardware nodes 1730 and radio units 17200.

With reference to FIG. 18, in accordance with an embodiment, acommunication system includes telecommunication network 1810, such as a3GPP-type cellular network, which comprises access network 1811, such asa radio access network, and core network 1814. Access network 1811comprises a plurality of base stations 1812 a, 1812 b, 1812 c, such asNBs, eNBs, gNBs or other types of wireless access points, each defininga corresponding coverage area 1813 a, 1813 b, 1813 c. Each base station1812 a, 1812 b, 1812 c is connectable to core network 1814 over a wiredor wireless connection 1815. A first UE 1891 located in coverage area1813 c is configured to wirelessly connect to, or be paged by, thecorresponding base station 1812 c. A second UE 1892 in coverage area1813 a is wirelessly connectable to the corresponding base station 1812a. While a plurality of UEs 1891, 1892 are illustrated in this example,the disclosed embodiments are equally applicable to a situation where asole UE is in the coverage area or where a sole UE is connecting to thecorresponding base station 1812.

Telecommunication network 1810 is itself connected to host computer1830, which may be embodied in the hardware and/or software of astandalone server, a cloud-implemented server, a distributed server oras processing resources in a server farm. Host computer 1830 may beunder the ownership or control of a service provider, or may be operatedby the service provider or on behalf of the service provider.Connections 1821 and 1822 between telecommunication network 1810 andhost computer 1830 may extend directly from core network 1814 to hostcomputer 1830 or may go via an optional intermediate network 1820.Intermediate network 1820 may be one of, or a combination of more thanone of, a public, private or hosted network; intermediate network 1820,if any, may be a backbone network or the Internet; in particular,intermediate network 1820 may comprise two or more sub-networks (notshown).

The communication system of FIG. 18 as a whole enables connectivitybetween the connected UEs 1891, 1892 and host computer 1830. Theconnectivity may be described as an over-the-top (OTT) connection 1850.Host computer 1830 and the connected UEs 1891, 1892 are configured tocommunicate data and/or signaling via OTT connection 1850, using accessnetwork 1811, core network 1814, any intermediate network 1820 andpossible further infrastructure (not shown) as intermediaries. OTTconnection 1850 may be transparent in the sense that the participatingcommunication devices through which OTT connection 1850 passes areunaware of routing of uplink and downlink communications. For example,base station 1812 may not or need not be informed about the past routingof an incoming downlink communication with data originating from hostcomputer 1830 to be forwarded (e.g., handed over) to a connected UE1891. Similarly, base station 1812 need not be aware of the futurerouting of an outgoing uplink communication originating from the UE 1891towards the host computer 1830.

Example implementations, in accordance with an embodiment, of the UE,base station and host computer discussed in the preceding paragraphswill now be described with reference to FIG. 19. In communication system1900, host computer 1910 comprises hardware 1915 including communicationinterface 1916 configured to set up and maintain a wired or wirelessconnection with an interface of a different communication device ofcommunication system 1900. Host computer 1910 further comprisesprocessing circuitry 1918, which may have storage and/or processingcapabilities. In particular, processing circuitry 1918 may comprise oneor more programmable processors, application-specific integratedcircuits, field programmable gate arrays or combinations of these (notshown) adapted to execute instructions. Host computer 1910 furthercomprises software 1911, which is stored in or accessible by hostcomputer 1910 and executable by processing circuitry 1918. Software 1911includes host application 1912. Host application 1912 may be operable toprovide a service to a remote user, such as UE 1930 connecting via OTTconnection 1950 terminating at UE 1930 and host computer 1910. Inproviding the service to the remote user, host application 1912 mayprovide user data which is transmitted using OTT connection 1950.

Communication system 1900 further includes base station 1920 provided ina telecommunication system and comprising hardware 1925 enabling it tocommunicate with host computer 1910 and with UE 1930. Hardware 1925 mayinclude communication interface 1926 for setting up and maintaining awired or wireless connection with an interface of a differentcommunication device of communication system 1900, as well as radiointerface 1927 for setting up and maintaining at least wirelessconnection 1970 with UE 1930 located in a coverage area (not shown inFIG. 19) served by base station 1920. Communication interface 1926 maybe configured to facilitate connection 1960 to host computer 1910.Connection 1960 may be direct or it may pass through a core network (notshown in FIG. 5) of the telecommunication system and/or through one ormore intermediate networks outside the telecommunication system. In theembodiment shown, hardware 1925 of base station 1920 further includesprocessing circuitry 1928, which may comprise one or more programmableprocessors, application-specific integrated circuits, field programmablegate arrays or combinations of these (not shown) adapted to executeinstructions. Base station 1920 further has software 1921 storedinternally or accessible via an external connection.

Communication system 1900 further includes UE 1930 already referred to.Its hardware 1935 may include radio interface 1937 configured to set upand maintain wireless connection 1970 with a base station serving acoverage area in which UE 1930 is currently located. Hardware 1935 of UE1930 further includes processing circuitry 1938, which may comprise oneor more programmable processors, application-specific integratedcircuits, field programmable gate arrays or combinations of these (notshown) adapted to execute instructions. UE 1930 further comprisessoftware 1931, which is stored in or accessible by UE 1930 andexecutable by processing circuitry 1938. Software 1931 includes clientapplication 1932. Client application 1932 may be operable to provide aservice to a human or non-human user via UE 1930, with the support ofhost computer 1910. In host computer 1910, an executing host application1912 may communicate with the executing client application 1932 via OTTconnection 1950 terminating at UE 1930 and host computer 1910. Inproviding the service to the user, client application 1932 may receiverequest data from host application 1912 and provide user data inresponse to the request data. OTT connection 1950 may transfer both therequest data and the user data. Client application 1932 may interactwith the user to generate the user data that it provides.

It is noted that host computer 1910, base station 1920 and UE 1930illustrated in FIG. 19 may be similar or identical to host computer1830, one of base stations 1812 a, 1812 b, 1812 c and one of UEs 1891,1892 of FIG. 18, respectively. This is to say, the inner workings ofthese entities may be as shown in FIG. 19 and independently, thesurrounding network topology may be that of FIG. 18.

In FIG. 19, OTT connection 1950 has been drawn abstractly to illustratethe communication between host computer 1910 and UE 1930 via basestation 1920, without explicit reference to any intermediary devices andthe precise routing of messages via these devices. Networkinfrastructure may determine the routing, which it may be configured tohide from UE 1930 or from the service provider operating host computer1910, or both. While OTT connection 1950 is active, the networkinfrastructure may further take decisions by which it dynamicallychanges the routing (e.g., on the basis of load balancing considerationor reconfiguration of the network).

Wireless connection 1970 between UE 1930 and base station 1920 is inaccordance with the teachings of the embodiments described throughoutthis disclosure. One or more of the various embodiments improve theperformance of OTT services provided to UE 1930 using OTT connection1950, in which wireless connection 1970 forms the last segment. Moreprecisely, the teachings of these embodiments may improve the latencyand power consumption and thereby provide benefits such as reduceddelays, better responsiveness, and extended battery lifetime.

A measurement procedure may be provided for the purpose of monitoringdata rate, latency and other factors on which the one or moreembodiments improve. There may further be an optional networkfunctionality for reconfiguring OTT connection 1950 between hostcomputer 1910 and UE 1930, in response to variations in the measurementresults. The measurement procedure and/or the network functionality forreconfiguring OTT connection 1950 may be implemented in software 1911and hardware 1915 of host computer 1910 or in software 1931 and hardware1935 of UE 1930, or both. In embodiments, sensors (not shown) may bedeployed in or in association with communication devices through whichOTT connection 1950 passes; the sensors may participate in themeasurement procedure by supplying values of the monitored quantitiesexemplified above, or supplying values of other physical quantities fromwhich software 1911, 1931 may compute or estimate the monitoredquantities. The reconfiguring of OTT connection 1950 may include messageformat, retransmission settings, preferred routing etc.; thereconfiguring need not affect base station 1920, and it may be unknownor imperceptible to base station 1920. Such procedures andfunctionalities may be known and practiced in the art. In certainembodiments, measurements may involve proprietary UE signalingfacilitating host computer 1910's measurements of throughput,propagation times, latency and the like. The measurements may beimplemented in that software 1911 and 1931 causes messages to betransmitted, in particular empty or ‘dummy’ messages, using OTTconnection 1950 while it monitors propagation times, errors etc.

FIG. 20 is a flowchart illustrating a method implemented in acommunication system, in accordance with one embodiment. Thecommunication system includes a host computer, a base station and a UEwhich may be those described with reference to FIGS. 18 and 19. Forsimplicity of the present disclosure, only drawing references to FIG. 20will be included in this section. In step 2010, the host computerprovides user data. In substep 2011 (which may be optional) of step2010, the host computer provides the user data by executing a hostapplication. In step 2020, the host computer initiates a transmissioncarrying the user data to the UE. In step 2030 (which may be optional),the base station transmits to the UE the user data which was carried inthe transmission that the host computer initiated, in accordance withthe teachings of the embodiments described throughout this disclosure.In step 2040 (which may also be optional), the UE executes a clientapplication associated with the host application executed by the hostcomputer.

FIG. 21 is a flowchart illustrating a method implemented in acommunication system, in accordance with one embodiment. Thecommunication system includes a host computer, a base station and a UEwhich may be those described with reference to FIGS. 18 and 19. Forsimplicity of the present disclosure, only drawing references to FIG. 21will be included in this section. in step 2110 of the method, the hostcomputer provides user data. In an optional substep (not shown) the hostcomputer provides the user data by executing a host application. In step2120, the host computer initiates a transmission carrying the user datato the UE. The transmission may pass via the base station, in accordancewith the teachings of the embodiments described throughout thisdisclosure. In step 2130 (which may be optional), the UE receives theuser data carried in the transmission.

FIG. 22 is a flowchart illustrating a method implemented in acommunication system, in accordance with one embodiment. Thecommunication system includes a host computer, a base station and a UEwhich may be those described with reference to FIGS. 18 and 19. Forsimplicity of the present disclosure, only drawing references to FIG. 22will be included in this section. In step 2210 (which may be optional),the UE receives input data provided by the host computer. Additionallyor alternatively, in step 2220, the UE provides user data. In substep2221 (which may be optional) of step 2220, the UE provides the user databy executing a client application. In substep 2211 (which may beoptional) of step 2210, the UE executes a client application whichprovides the user data in reaction to the received input data providedby the host computer. In providing the user data, the executed clientapplication may further consider user input received from the user.Regardless of the specific manner in which the user data was provided,the UE initiates, in substep 2230 (which may be optional), transmissionof the user data to the host computer. In step 2240 of the method, thehost computer receives the user data transmitted from the UE, inaccordance with the teachings of the embodiments described throughoutthis disclosure.

FIG. 23 is a flowchart illustrating a method implemented in acommunication system, in accordance with one embodiment. Thecommunication system includes a host computer, a base station and a UEwhich may be those described with reference to FIGS. 18 and 19. Forsimplicity of the present disclosure, only drawing references to FIG. 23will be included in this section. In step 2310 (which may be optional),in accordance with the teachings of the embodiments described throughoutthis disclosure, the base station receives user data from the UE. Instep 2320 (which may be optional), the base station initiatestransmission of the received user data to the host computer. In step2330 (which may be optional), the host computer receives the user datacarried in the transmission initiated by the base station.

Any appropriate steps, methods, features, functions, or benefitsdisclosed herein may be performed through one or more functional unitsor modules of one or more virtual apparatuses. Each virtual apparatusmay comprise a number of these functional units. These functional unitsmay be implemented via processing circuitry, which may include one ormore microprocessor or microcontrollers, as well as other digitalhardware, which may include digital signal processors (DSPs),special-purpose digital logic, and the like. The processing circuitrymay be configured to execute program code stored in memory, which mayinclude one or several types of memory such as read-only memory (ROM),random-access memory (RAM), cache memory, flash memory devices, opticalstorage devices, etc. Program code stored in memory includes programinstructions for executing one or more telecommunications and/or datacommunications protocols as well as instructions for carrying out one ormore of the techniques described herein. In some implementations, theprocessing circuitry may be used to cause the respective functional unitto perform corresponding functions according one or more embodiments ofthe present disclosure.

Generally, all terms used herein are to be interpreted according totheir ordinary meaning in the relevant technical field, unless adifferent meaning is clearly given and/or is implied from the context inwhich it is used. All references to a/an/the element, apparatus,component, means, step, etc. are to be interpreted openly as referringto at least one instance of the element, apparatus, component, means,step, etc., unless explicitly stated otherwise. The steps of any methodsdisclosed herein do not have to be performed in the exact orderdisclosed, unless a step is explicitly described as following orpreceding another step and/or where it is implicit that a step mustfollow or precede another step. Any feature of any of the embodimentsdisclosed herein may be applied to any other embodiment, whereverappropriate. Likewise, any advantage of any of the embodiments may applyto any other embodiments, and vice versa. Other objectives, features andadvantages of the enclosed embodiments will be apparent from thedescription.

Some of the embodiments contemplated herein are described more fullywith reference to the accompanying drawings. Other embodiments, however,are contained within the scope of the subject matter disclosed herein,and the disclosed subject matter should not be construed as limited toonly the embodiments set forth herein; rather, these embodiments areprovided by way of example to convey the scope of the subject matter tothose skilled in the art.

What is claimed is:
 1. A method performed by a user equipment, themethod comprising: receiving at the user equipment, from a source radioaccess network, RAN, node with which the user equipment has a connection(16), a message indicating that the connection is to be suspended andindicating a resume identifier usable by the user equipment to resumethe connection after the connection is suspended; while the connectionis suspended, transmitting from the user equipment to a target RAN nodea request to resume the connection, wherein the request includes theresume identifier; and transmitting from the user equipment to thetarget RAN node an indication of a public land mobile network, PLMN,with which the resume identifier is associated.
 2. The method of claim1, further comprising receiving a paging message that includes theresume identifier and an indication of the PLMN associated with theresume identifier, wherein transmitting the request to resume theconnection is performed responsive to receiving the paging message.3.-10. (canceled)
 11. The method of claim 1, wherein the indication of aPLMN with which the resume identifier is associated is an indication ofa PLMN with which the user equipment is registered or an indication of aPLMN selected by the user equipment.
 12. The method of claim 1, whereinthe indication of the PLMN with which the resume identifier isassociated comprises an index of a specific PLMN identity in a list ofPLMN identities, wherein each PLMN identity in the list has anassociated index. 13.-21. (canceled)
 22. A user equipment comprising:processing circuitry to: receive, from a source radio access network,RAN, node with which the user equipment has a connection, a messageindicating that the connection is to be suspended and indicating aresume identifier usable by the user equipment to resume the connectionafter the connection is suspended; while the connection is suspended,transmit to a target RAN node a request to resume the connection,wherein the request includes the resume identifier; and transmit to thetarget RAN node an indication of a public land mobile network, PLMN,with which the resume identifier is associated.
 23. The user equipmentof claim 22, wherein the processing circuitry is further to receive apaging message that includes the resume identifier and an indication ofthe PLMN associated with the resume identifier, wherein the processingcircuitry is configured to transmit the request to resume the connectionresponsive to receiving the paging message.
 24. The user equipment ofclaim 2, wherein the resume identifier is associated with a RAN nodeidentity that identifies, using a RAN node addressing space shared bydifferent PLMNs, a RAN node which maintains a context for the connectionwhile the connection is suspended.
 25. The user equipment of claim 22,wherein different PLMNs have the same set of resume identifiers usableby user equipments to resume suspended connections.
 26. The userequipment of claim 22, wherein the indication of a PLMN with which theresume identifier is associated is an indication of a PLMN with whichthe user equipment is registered or an indication of a PLMN selected bythe user equipment.
 27. The user equipment of claim 22, wherein theindication of the PLMN with which the resume identifier is associatedcomprises an index of a specific PLMN identity in a list of PLMNidentities, wherein each PLMN identity in the list has an associatedindex. 28.-43. (canceled)
 44. A non-transitory device-readable mediumhaving stored thereon instructions that, when executed by processingcircuitry of a user equipment, cause the user equipment to: receive,from a source radio access network, RAN, node with which the userequipment has a connection, a message indicating that the connection isto be suspended and indicating a resume identifier usable by the userequipment to resume the connection after the connection is suspended;while the connection is suspended, transmit to a target RAN node arequest to resume the connection, wherein the request includes theresume identifier; and transmit to the target RAN node an indication ofa public land mobile network, PLMN, with which the resume identifier isassociated. 45.-46. (canceled)
 47. The non-transitory device-readablemedium of claim 44, when the instructions further cause the userequipment to: receive a paging message that includes the resumeidentifier and an indication of the PLMN associated with the resumeidentifier; and transmit the request to resume the connection responsiveto receiving the paging message.
 48. The non-transitory device-readablemedium of claim 44, wherein the indication of a PLMN with which theresume identifier is associated is an indication of a PLMN with whichthe user equipment is registered or an indication of a PLMN selected bythe user equipment.
 49. The non-transitory device-readable medium ofclaim 44, wherein the indication of the PLMN with which the resumeidentifier is associated comprises an index of a specific PLMN identityin a list of PLMN identities, wherein each PLMN identity in the list hasan associated index.
 50. The non-transitory device-readable medium ofclaim 44, wherein the indication of a PLMN is included within therequest to resume the connection.
 51. The non-transitory device-readablemedium of claim 44, wherein the indication of a PLMN is included in aseparate message from the request to resume the connection.
 52. Thenon-transitory device-readable medium of claim 51, wherein the separatemessage is a resume complete message.
 53. The method of claim 1, whereinthe indication of a PLMN is included in a separate message from therequest to resume the connection.
 54. The method of claim 53, whereinthe separate message is a resume complete message.
 55. The userequipment of claim 22, wherein the indication of a PLMN is included in aseparate message from the request to resume the connection, and whereinthe separate message is a resume complete message.